Re: IDE is very slow because of Output window
From: Steve McLellan (sjm.NOSPAM)
Date: 10/26/04
- Next message: Jason: "RE: Office Add-in. Trapping/Redirecting CTRL-S"
- Previous message: Roy Chastain: "How can you call managed code without hosting the CLR"
- In reply to: James_at_avecsys: "IDE is very slow because of Output window"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 26 Oct 2004 16:44:24 +0100
Try turning on 'break on exceptions' - then you'll be able to track down the
problem. If it's slow when the Output window's closed, it's probably because
there are loads of exceptions getting thrown everywhere, which usually isn't
especially good.
Steve
"James@avecsys" <james@discussion.microsoft.com> wrote in message
news:1638AA47-04B3-4AF0-BD30-145E92726E60@microsoft.com...
>I have a C# WinForms app which reuses unmanaged C++ dlls using COM interop.
> When I debug the app by running the code in the IDE, it is very very slow.
> In
> fact almost too slow to use. However, when I run the .exe, it is very very
> fast. I have noticed huge numbers of lines of info being printed out in
> the
> Output window. For example "First-chance exception at 0x77e73887 in
> Catapult.exe: 0xE0000001: 0xe0000001.". I see this a lot. I believe this
> is
> slowing the IDE down and it doesn't matter whether the Output window is
> being
> displayed or not. I do not see this if I use the COM dlls from the VB6
> IDE.
> This is obviously a "new feature" with the .NET IDE. I really need to turn
> off this output if I am to effectively debug my app. Is there a way I can
> do
> this?
> Thanks
> James
- Next message: Jason: "RE: Office Add-in. Trapping/Redirecting CTRL-S"
- Previous message: Roy Chastain: "How can you call managed code without hosting the CLR"
- In reply to: James_at_avecsys: "IDE is very slow because of Output window"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|