devenv.exe CPU 100%

D

Dave

How do I disable the syntax compiler or background compiler in VB.NET ?
This has got to be the reason why my CPU is always at 100 percent while I'm
editing one of my VB.NET projects. It doesn't do it on all of them but this
one it does. I basically only want it to compile when I do a build or a
start debug. Does anyone know what setting I need to enable/disable ?

My machine is more than adequately configured. 2 gig of memory, plenty of
disk space 4+ gighertz CPU. Visual Studio 2005 just seems to sit and grind
on large projects in the IDE.

Anyone have any idea's ?
 
K

Ken Tucker [MVP]

Hi,

A hot fix that addresses some performance issues with Visual Basic 2005 has
been released.If you are having the problems listed in the KB article call
PSS (Product Support Services) 800-936-4900 (US phone #) and tell Technical
Routers that they want to be transferred to Developer Support, Visual Basic
team, it would expedite the call. Request the hot fix described in KB
Article 917452. The KB article is not available yet.

Ken
 
G

Gary Chang[MSFT]

Hi Dave,

Just as MVP Ken suggested, currently we have a hotfix to resolve such a
problem. You can contact our PSS to request that hotfix. This may require
you to submit a support incident in Microsoft PSS (Product Support
Service). As a MSDN subscriber, you have two free support incidents.

By the way, since this problem is a product issue, PSS won't charge money.
Every MSDN subscriber has two free support incidents. You could use one of
them to contact Microsoft PSS. So you don't need to pay money yet. If the
problem is confirmed by Microsoft PSS as a product issue, you still have
two free support incidents.

For your reference, I have attached steps to contact Microsoft PSS here:
You can contact Microsoft Product Support directly to discuss additional
support options you may have available, by contacting us at 1-(800)936-5800
or by choosing one of the options listed at:

http://support.microsoft.com/common/international.aspx?rdpath=gp;en-us;offer
prophone

Thanks!

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
C

Carlos J. Quintero [VB MVP]

Hi Ken,

If the KB article is not available yet, how can we know if we are having the
problems listed in it? Is it an article that will be public or only for
partners / MVPs?

--

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio
You can code, design and document much faster:
http://www.mztools.com
 
D

Dave

Is there any time table on when the hotfix will be available or more details
about what the real problem is ? If it's related to some of the VB
Compatibility stuff that VS 2005 puts into the project I could go in and get
rid of as much of it as I can. I've already removed a large majority of the
compatibility stuff that gets put in. I really only have the control arrays
still in there maybe a few other things.

or is it related to a particular reference of some sort ?

or do I need to make the phone call, I really hate to spend that much time
on the phone, is this a lengthy process to actually gain access to this
hotfix ?

Dave
 
C

Carlos J. Quintero [VB MVP]

Dave said:
Is there any time table on when the hotfix will be available or more
details
about what the real problem is ? If it's related to some of the VB
Compatibility stuff that VS 2005 puts into the project I could go in and
get
rid of as much of it as I can. I've already removed a large majority of
the
compatibility stuff that gets put in. I really only have the control
arrays
still in there maybe a few other things.

or is it related to a particular reference of some sort ?

or do I need to make the phone call, I really hate to spend that much time
on the phone, is this a lengthy process to actually gain access to this
hotfix ?

Dave

"Gary Chang[MSFT]" said:
Hi Dave,

Just as MVP Ken suggested, currently we have a hotfix to resolve such a
problem. You can contact our PSS to request that hotfix. This may require
you to submit a support incident in Microsoft PSS (Product Support
Service). As a MSDN subscriber, you have two free support incidents.

By the way, since this problem is a product issue, PSS won't charge
money.
Every MSDN subscriber has two free support incidents. You could use one
of
them to contact Microsoft PSS. So you don't need to pay money yet. If the
problem is confirmed by Microsoft PSS as a product issue, you still have
two free support incidents.

For your reference, I have attached steps to contact Microsoft PSS here:
You can contact Microsoft Product Support directly to discuss additional
support options you may have available, by contacting us at 1-(800)936-5800
or by choosing one of the options listed at:

http://support.microsoft.com/common/international.aspx?rdpath=gp;en-us;offer
prophone

Thanks!

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
C

Carlos J. Quintero [VB MVP]

Hi Dave,

The VS 2005 SP1, which includes hot fixes (more tested), is scheduled for Q3
2006, so you may want to get the hotfix now. It's not actuallay a lengthly
process if you say that you want a hotfix and point them to the specific KB
article about it. You receive a download URL it by e-mail in a matter of
hours. I've done it a couple of times.

--

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio
You can code, design and document much faster:
http://www.mztools.com
 
D

Dave

Got the hot fix, seems like it does fix some of the conditions but I'm not
sure it gets all of them. Seems like there's combinations of displaying
converted forms in the designer and viewing the class diagram simultaneously
puts the CPU at 100%. I need to dig into this a little more.


Dave said:
Is there any time table on when the hotfix will be available or more details
about what the real problem is ? If it's related to some of the VB
Compatibility stuff that VS 2005 puts into the project I could go in and get
rid of as much of it as I can. I've already removed a large majority of the
compatibility stuff that gets put in. I really only have the control arrays
still in there maybe a few other things.

or is it related to a particular reference of some sort ?

or do I need to make the phone call, I really hate to spend that much time
on the phone, is this a lengthy process to actually gain access to this
hotfix ?

Dave

"Gary Chang[MSFT]" said:
Hi Dave,

Just as MVP Ken suggested, currently we have a hotfix to resolve such a
problem. You can contact our PSS to request that hotfix. This may require
you to submit a support incident in Microsoft PSS (Product Support
Service). As a MSDN subscriber, you have two free support incidents.

By the way, since this problem is a product issue, PSS won't charge money.
Every MSDN subscriber has two free support incidents. You could use one of
them to contact Microsoft PSS. So you don't need to pay money yet. If the
problem is confirmed by Microsoft PSS as a product issue, you still have
two free support incidents.

For your reference, I have attached steps to contact Microsoft PSS here:
You can contact Microsoft Product Support directly to discuss additional
support options you may have available, by contacting us at 1-(800)936-5800
or by choosing one of the options listed at:
http://support.microsoft.com/common/international.aspx?rdpath=gp;en-us;offer
prophone

Thanks!

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
K

Ken Halter

"Gary Chang[MSFT]" said:
Hi Dave,

Just as MVP Ken suggested, currently we have a hotfix to resolve such a
problem. You can contact our PSS to request that hotfix.

Here comes 2 (deflated) cents...

fwiw, I find it >>incredibly<< annoying to have to call support, and
potentially pay for the call, for something that should (imo) be available
for download to anyone that wants it. Even more annoying when these
"hotfixes" don't make it into a service pack at one point or another. Since
I'm a "VB5/6'er", I've had to deal with these kinds of issues for over a
decade.

imo, It's a file... if it truly fixes a known problem, release it to the
public and don't bog support phone lines down with download requests or
force customers to make the call themselves.... and, above all, don't charge
people for something that should be available as part of their paid Visual
Studio license (aka a development environment that works "as advertised") in
the first place.
 
D

Dave

They agreed not to charge me an incident against my MSDN 2 incidents a year.
So they said. Who knows I may have gotten dinked in either case.

There is definitely something funky about the way these compatibility
projects function in VB 2005. The hotfix definitely does fix certain
issues. I can't definitively tell you what because I would have to
uninstall my hotfix to determine that.

Things do seem to be better, I've been in the optimization phase of my
project conversion. I'm now trying to remove the remaining VB6isms. The
only thing I don't really have a replacement for is the control array logic.

Seems like I either have to use what is provided in the VB6 compatibility or
create my own class to do it.


Ken Halter said:
"Gary Chang[MSFT]" said:
Hi Dave,

Just as MVP Ken suggested, currently we have a hotfix to resolve such a
problem. You can contact our PSS to request that hotfix.

Here comes 2 (deflated) cents...

fwiw, I find it >>incredibly<< annoying to have to call support, and
potentially pay for the call, for something that should (imo) be available
for download to anyone that wants it. Even more annoying when these
"hotfixes" don't make it into a service pack at one point or another. Since
I'm a "VB5/6'er", I've had to deal with these kinds of issues for over a
decade.

imo, It's a file... if it truly fixes a known problem, release it to the
public and don't bog support phone lines down with download requests or
force customers to make the call themselves.... and, above all, don't charge
people for something that should be available as part of their paid Visual
Studio license (aka a development environment that works "as advertised") in
the first place.
 
G

Gary Chang[MSFT]

That's great, Dave!

Such a problem is caused by the performance issues in the Visual Basic
2005 compiler, I am glad to know that hotfix works for you.

Have a nice day!

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
D

Dave

So have you installed this Hotfix Ken ?


Ken Halter said:
"Gary Chang[MSFT]" said:
Hi Dave,

Just as MVP Ken suggested, currently we have a hotfix to resolve such a
problem. You can contact our PSS to request that hotfix.

Here comes 2 (deflated) cents...

fwiw, I find it >>incredibly<< annoying to have to call support, and
potentially pay for the call, for something that should (imo) be available
for download to anyone that wants it. Even more annoying when these
"hotfixes" don't make it into a service pack at one point or another. Since
I'm a "VB5/6'er", I've had to deal with these kinds of issues for over a
decade.

imo, It's a file... if it truly fixes a known problem, release it to the
public and don't bog support phone lines down with download requests or
force customers to make the call themselves.... and, above all, don't charge
people for something that should be available as part of their paid Visual
Studio license (aka a development environment that works "as advertised") in
the first place.
 
R

rvgrahamsevatenein

Just piping in to say I've obtained and installed the hotfix, and it's
working well for me.

I was having a major problem with the Ctl + Shift + H replace word
function, which I use a lot. After replacing all instances of a word,
the environment would stay locked up for up to several minutes,
consuming a slowly decaying amount of cpu cycles. I couldn't even close
the replace word dialog. Also the environment was extremely slow to
load a vb project, and equally slow to return to edit mode after
closing a debug run.

It seems to me this problem cropped up after installing Sql 2005 Sp1.
But that seems unlikely to be connected since this issue is specific to
the vb compiler.

Thanks all, Bob
 
D

Dave

I installed it too, it definitely does fix a lot of performance problems in
VB.Net, however I do think there are more to fix.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top