I am experiencing the same problem as listed by a number of other questions
here whereby the vs2003 editor hangs for around 10 seconds, even if only
moving the insertion point to another line of code. The editor usually can
still take keyboard input so i'm guessing that it's running on a different
thread to whatever is apparently locking the IDE (Intellisense maybe?).

There also seem to be a lot of questions here that have not had responses. I
thought that Microsoft guarentee to post an answer withing two working days
at the moment??

Please let me know if anyone knows of any work arounds or fixes for this as
it's slowly driving me mad!

Cheers,
Rob

Hi Rob,

>I am experiencing the same problem as listed by a number of other
questions
>here whereby the vs2003 editor hangs for around 10 seconds, even if only
>moving the insertion point to another line of code. The editor usually can
>still take keyboard input so i'm guessing that it's running on a different
>thread to whatever is apparently locking the IDE (Intellisense maybe?).

I am not entirely clear what "the same problem" you mentioned here? Do you
refer to a problem which is discussed in another newsgroup post? If so,
could you please give me its link?

If your problem is that the VS.NET 2003 IDE will hang for some time when
you edit your program in the code editor, would you please tell me whether
the problem only happens to a specific project, or just happens randomly
regardless of the projects in working?


Thanks!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C http://www.microsoft.com/security/
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/service...=en-us&gssnb=1
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Gary,
Thanks for coming back so quick!
If you do a search in the vsnet.ide newsgroup searching for hangs, you
should see a number of posts relating to the editor hanging under certain
circumstances. The one that is closest to what I (and two other developers
here) has the subject line '.Net IDE hangs ~10 seconds while editing files'.

The problem is as you guess, if I edit the code via the code editor, or even
just move the insertion point around, the IDE appears to freeze for around
5-10 seconds. During this time I can still type into the code editor even
though there are no visual clues that this can be done (the cursor disappears
etc.).

This behaviour appears randomly now and again within this project, but we
have had it occur in other projects as well. Restarting VS does not rectify
the situation, nor does rebooting the machine.

It appears that this only occurs under certain cirumstances (which I can't
work out what) and then goes back to working normally.

Cheers,
Rob

"Gary Chang[MSFT]" wrote:
[..]

Hi Rob,

Thanks for your information!

I have found that post you figured, which is talked about a VB.NET project,
do you have same problem with the VB.NET project?

If so, there is a known issue of when the VS.NET IDE loads a large VB
solution.
The VB compiler is working to generate task list errors and updated
intellisense information and it could take time if the solution is very
large.

In this scenario. I suggest you improve performance by referencing dlls
instead of creating project to project references in one big solution (I
mean make your solution only load the project that you are actually working
on and create a file reference(dll) to the other projects).


Thanks!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C http://www.microsoft.com/security/
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/service...=en-us&gssnb=1
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Gary,

I suspected that something was going on in the background like this. The
solution is big, but this wouldn't explain why it will suddenly suffer from
the hangs, and then at some point (normally a couple of days later) revert to
working normally. I know that there are issues around the IDE where it can
sometimes not work out which assemblies need to be recompiled (links below)
and only a 'rebuild all' works (which I see a lot in this project), maybe the
two things are related?

Cheers,
Rob

http://www.panopticoncentral.net/arc...03/19/291.aspx
http://weblogs.asp.net/grobinson/arc.../29/46357.aspx


"Gary Chang[MSFT]" wrote:
[..]

Hi Gary,

> I have found that post you figured, which is talked about a VB.NET
> project,
> do you have same problem with the VB.NET project?
>
> If so, there is a known issue of when the VS.NET IDE loads a large VB
> solution.
> The VB compiler is working to generate task list errors and updated
> intellisense information and it could take time if the solution is very
> large.

Given that it can also happen with unmanaged C++ solutions, even small ones
(one project or 80, it doesn't seem to make much difference) I can't see
this being a VB.NET specific issue.

Could it be related to source code control? All of our projects are SCC
enabled, and sometimes such a delay happens when you start typing and the
IDE needs to check out the file. Sometimes, but not always).

I've seen the IDE go to sleep for a minute or more, but 10-20 seconds is
more typical.


Kind Regards,

Anna-Jayne Metcalfe

Software/Product Development Consultant,
Riverblade Limited.
http://www.riverblade.co.uk

Hi Rob,

>..., The solution is big, but this wouldn't explain why it will suddenly
suffer
>from the hangs, and then at some point (normally a couple of days later)
>revert to working normally.
>...

Maybe this is another symptom of the issue I mentioned in the last message,
I think it would be a good many amount of your solution's code needs to be
updated sometimes, so the compiler will take more time to re-compile it,
then the intellisence database is inaccessible at that time. And this could
also explain why a 'rebuild all' will work.


Thanks!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C http://www.microsoft.com/security/
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/service...=en-us&gssnb=1
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Anna,

>Given that it can also happen with unmanaged C++ solutions, even
> small ones (one project or 80, it doesn't seem to make much difference)
> I can't see this being a VB.NET specific issue.

For a unmanaged C++ project, it may be caused by its intellisence database
file(.ncb file) corruptted, you can delete that file and open the project
in the IDE to let the VS.NET recreate it again.


Thanks!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C http://www.microsoft.com/security/
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/service...=en-us&gssnb=1
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Gary,

> For a unmanaged C++ project, it may be caused by its intellisence database
> file(.ncb file) corruptted, you can delete that file and open the project
> in the IDE to let the VS.NET recreate it again.

Thanks. :)

Is there any possibility that this is fixed in VS2005 and in a possible
service pack for VS2003?


Kind Regards,

Anna-Jayne Metcalfe

Software/Product Development Consultant,
Riverblade Limited.
http://www.riverblade.co.uk

Anna-Jayne Metcalfe wrote:
> Hi Gary,
>>>For a unmanaged C++ project, it may be caused by its intellisence database
>>file(.ncb file) corruptted, you can delete that file and open the project
>>in the IDE to let the VS.NET recreate it again.
>> Thanks. :)
>
> Is there any possibility that this is fixed in VS2005 and in a possible
> service pack for VS2003?
>

Don't you know? 2005 *will be* the SP for 2003.

Gee... do you think I'm bitter over the way bugs were treated in the
..NET => 2003 changeover?

red floyd <no.spam> wrote:

> Don't you know? 2005 *will be* the SP for 2003.

LOL. Yup, except that we have to pay for the bug fixes. And it'll be
released ANY YEAR NOW! :-)

> Gee... do you think I'm bitter over the way bugs were treated in the
> .NET => 2003 changeover?

Well, I certainly am. I thought VS.NET was pretty cool when I first got it,
but I've lost that respect, solely over the lack of attention to problems
that we have to deal with on a daily basis.

Hi Anna-Jayne

>Is there any possibility that this is fixed in VS2005 and in a possible
>service pack for VS2003?

Both of the products--- VS.NET 2005 and the service pack for the VS.NET
2003 are not released yet, currently they are still in the development and
test stages, so at this time I am afraid we could not give you a
confirmative answer on this issue.

However since this problem is already a known issue to the VS.NET 2003, our
corresponding product teams should have made some improvement about it.


Thanks for your understanding!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C http://www.microsoft.com/security/
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/service...=en-us&gssnb=1
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.

Quick question Does this hanging situation happen after you close out of the
VS.net in any other apps before you reboot after experiencing the hangs?

"RMW" wrote:
[..]

Gary, et al
I understand what might be happening with multi-project
solutions and/or multi-language projects. But what about
a one project solution and one language (vb).

Is this what we are dealing with?

http://support.microsoft.com/default...b;en-us;824580

regards
grondoudis

"Gary Chang[MSFT]" wrote:
[..]