Re: Why no patch for the anoying Visual Basic compiler problem
- From: "Chris" <consult_Chris@xxxxxxxxxxxxxxxx>
- Date: Mon, 16 Oct 2006 20:45:47 -0400
Dennis,
You have to call Microsoft when you want to obtain a hotfix that has not
been regression tested. Basically, it's not ready for prime time.
Call Microsoft.
Go through the menu system and there will be an option "if you need a
hotfix, press"
This will get you to a non-technical person that will log your information
and e-mail you the hotfix--no charge.
Even if you mistakenly press the option to speak with tech support (PSS) if
you tell them that you need a hotfix you never get charged. At no time have
I ever had to give Microsoft my billing information.
Chris
"Dennis" <Dennis@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6D3211F7-259F-4416-B7C1-081ADC0D0819@xxxxxxxxxxxxxxxx
Do you know why M'soft has to be called to get a hotfix? If they don't
think
the hotfix will solve the problem, they they want to charge for the call.
At
least that's the way I understand it. Why don't they just post the
hotfixes
so we can download them and see if that fixes our problems?
--
Dennis in Houston
"Chris" wrote:
Hey sqlguy,
I heard that turning off background compilation was a work around a while
ago. However, they do have a few hotfixes available.
FIX: You may receive Visual Basic compiler error messages when you
are
developing a Visual Basic 2005 project in Visual Studio 2005
(915038) - This problem is caused by a bug in the Visual Basic 2005
compiler. ... Therefore, if you are not severely affected by this
problem,
we recommend that you wait for the next Microsoft Visual Studio 2005
service
pack that contains this hotfix.
http://support.microsoft.com/kb/915038/en-us
FIX: You may experience performance issues when you use solutions
that
contain large Visual Basic projects in Visual Studio 2005
(917452) - Fixes a problem where you experience poor performance in
the Visual Studio 2005 IDE when you use a Visual Basic solution that
contains large projects.
http://support.microsoft.com/kb/917452/en-us
There was also KB 920857, which I cannot find on Microsoft's website, yet
have the file from when I called Microsoft and they sent a 2 or 3 of
patches
to me. Maybe another KB article supersedes 920857.
The bottom line is you really need to call Microsoft to get the hotfixes
that they have to Visual Basic 2005. Additionally, the call for the
hotfix(s) are free and even if you call to speak to PSS, if they deem
that
your problem can be fixed by a hotfix they don't make you pay for the
call.
Chris
"sqlguy" <lloyd.sheen@xxxxxxxxx> wrote in message
news:1161016749.323387.72340@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Why do we have to contact MS for a problem that has been with this
compiler from at least the beta of VS 20005. I am so sick and tired of
the 30 - 40 clicks it takes to dismiss VS when there is a problem. Can
they not just post the fix. I see no reason to contact MS since I have
most likely sent about 1500 dumps to them and I would think this would
get their attention.
.
- References:
- Prev by Date: Repeater control question..
- Next by Date: Re: What .NET classes are SLOW vs. API?
- Previous by thread: Re: Why no patch for the anoying Visual Basic compiler problem
- Next by thread: Re: Why no patch for the anoying Visual Basic compiler problem
- Index(es):
Relevant Pages
|
