Re: Delphi 2005 Update 4 IS needed !!!



Dan Miser wrote:
I love how D2005 Enterprise works, too. People will read the negative and give it far more weight than reading the positive and believing it. I don't really care. I'll just keep pluuging away happily while others stand on the sidelines.

I like how it works as well, when it works. DCM'ed Win32 is ok, rarely any problems. Full version to do VCL.NET crashes on me very frequently, though.


1. Loading - Sometimes it doesn't even load, just hangs and I have to kill it with task manager. It seems, but isn't certain, that bringing another app to the foreground while the splash screen is up either triggers it or makes it happen more often. If I sit there for the whole 1+ minute load, it doesn't seem to happen.

2. Whatever you call the bit where leaving the mouse over a word shows the unit/assembly the word is declared in, plus the calling convention if it is a function or procedure will occasionally hang the whole system. This seems to happen if you pull the mouse away after the box is drawn but before the text is filled in, and where your mouse moves is another identifier. Again, while it happens a lot, it isn't 100% reproducable.

3. App crashes running in IDE give 0 output as to why in some cases. It seems that it happens when calling an unmanaged DLL entry with incorrectly marshalled parameters. The app hits the offending call and simply terminates. No debugger window, no exception, no nothing, just bam, back to the IDE. Doesn't matter if you just run, or single step. This isn't the disappearing IDE problem. I've never seen that one.

4. Failure to shutdown. Occasionally, when you shut it down, it hangs and has to be killed with task manager. This is rarer than the others, and I don't particularly mind it.

These issues make using VCL.NET a pain. I don't use this for my own apps, but I need to develop an assembly for someone else, and so I have my test code as VCL.NET for now. The assembly won't have any GUI, but it is easier to test the code that will go into it this way. If I had to do more than a trivial wrapper app this way, I'd scream. However, since doing some work in eVC++ a few months ago, I'm used to buggy IDE's that crash. :) Fortunately, the Win32 only config from DCM has none of these problems, and I have released one larger app with it, and am not worried about others should I feel I need to migrate them from D6.

Jeff.

P.S. System is WinXPSP2, D2005 update 3 applied
.



Relevant Pages

  • Re: Walkthrough Instruction Error
    ... Well what you didn't say was that your code couldn't be run from the IDE. ... Whether or not it is in process or out of process is in itself insignificant, what is important is the overhead of marshalling and synchronization. ... The only advantage out of process has is it doesn't necessarily pull the app down if it crashes. ...
    (microsoft.public.vb.general.discussion)
  • Re: You finally beat me down
    ... I have spent a number of years developing a certain app ... ... installing components crash the IDE? ... Your stock VCL controls lack the most basic functionality. ... native app to build, it will be in WTL/wxWidgets or QT. ...
    (borland.public.delphi.non-technical)
  • Re: Great SWT Program
    ... functionality I'll use a *real* IDE like Eclipse. ... emacs, but eclipse is also a vastly superior IDE with, particularly, a ... then I don't need the app to be able to do ... Running it 1000 times in a loop makes this especially visible. ...
    (comp.lang.java.programmer)
  • Re: How to debug an ActiveX DLL
    ... You don't even need the main application in the IDE Dag. ... Just loaded the VB project for the DLL into the IDE, ... instruct it to run your main app whenever you want to debug the VB DLL. ... I'm a real novice when it comes to ActiveX DLLs, ...
    (comp.lang.basic.visual.misc)
  • Re: .net IDE Shuts Down during a build
    ... I did not get to try your solution coz .. ... Shut down the IDE ... Then envoke the web app from the browser, then open the IDE, then ... > which you can re-enable the network connections and the IDE seems to be OK ...
    (microsoft.public.vsnet.ide)