"Dave" <KingOfTheBeach@community.nospam> wrote in message
news:uqYQSrlYGHA.4432@TK2MSFTNGP04.phx.gbl...
> 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 ?
>
>

"Ken Tucker [MVP]" <vb***@bellsouth.net> escribió en el mensaje
news:e5kMBxoYGHA.1192@TK2MSFTNGP03.phx.gbl...
> 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

"Carlos J. Quintero [VB MVP]" <carlosq@NOSPAMsogecable.com> wrote in message
news:ut0td0sYGHA.4688@TK2MSFTNGP04.phx.gbl...
> 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
>
>
> "Ken Tucker [MVP]" <vb***@bellsouth.net> escribió en el mensaje
> news:e5kMBxoYGHA.1192@TK2MSFTNGP03.phx.gbl...
>> 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
>
>

news:Pc7JRQrYGHA.880@TK2MSFTNGXA01.phx.gbl...
> 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

> 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.
>
>

"Dave" <KingOfTheBeach@community.nospam> escribió en el mensaje
news:OQF9rNvYGHA.4760@TK2MSFTNGP03.phx.gbl...
> 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]"" <v-gar***@online.microsoft.com> wrote in message
> news:Pc7JRQrYGHA.880@TK2MSFTNGXA01.phx.gbl...
>> 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.
>>
>>
>
>

"Dave" <KingOfTheBeach@community.nospam> escribió en el mensaje
news:OQF9rNvYGHA.4760@TK2MSFTNGP03.phx.gbl...
> 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
>

"Dave" <KingOfTheBeach@community.nospam> wrote in message
news:OQF9rNvYGHA.4760@TK2MSFTNGP03.phx.gbl...
> 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]"" <v-gar***@online.microsoft.com> wrote in message
> news:Pc7JRQrYGHA.880@TK2MSFTNGXA01.phx.gbl...
> > 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:
> >
> >
>

> > 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.
> >
> >
>
>

"Ken Halter" <Ken_Halter@Use_Sparingly_Hotmail.com> wrote in message
news:e612f6yYGHA.4884@TK2MSFTNGP02.phx.gbl...
> ""Gary Chang[MSFT]"" <v-gar***@online.microsoft.com> wrote in message
> news:Pc7JRQrYGHA.880@TK2MSFTNGXA01.phx.gbl...
> > 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.
>
> --
> Ken Halter - MS-MVP-VB (visiting from VB6 world) - http://www.vbsight.com
> Please keep all discussions in the groups..
>
>

"Ken Halter" <Ken_Halter@Use_Sparingly_Hotmail.com> wrote in message
news:e612f6yYGHA.4884@TK2MSFTNGP02.phx.gbl...
> ""Gary Chang[MSFT]"" <v-gar***@online.microsoft.com> wrote in message
> news:Pc7JRQrYGHA.880@TK2MSFTNGXA01.phx.gbl...
> > 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.
>
> --
> Ken Halter - MS-MVP-VB (visiting from VB6 world) - http://www.vbsight.com
> Please keep all discussions in the groups..
>
>

news:1146785770.591669.287530@j33g2000cwa.googlegroups.com...
> 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
>