VS 2003 Very Slow

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

I have a form containing a lot of various forms objects (about 120-150). It
takes about 10 minutes for the solution to load (only one project). If I
modify the corresponding .h file and return to the [Design] tab the IDE
become unresponsive to about 5-10 minutes again. For example, if I double
click on a label, the .h code window appears with the corresponding event
handling function for 'Click'. If I delete that function and then return to
the [Deisgn] tab, it takes, and I just tested this, 12 minutes before VS2003
IDE becomes reponsive again and actually shows the Design window. Its obvious
that when I deleted the event hanlding function, VS2003 needed to remove the
corresponding '.. new System::EventHandler ..' line located in the
InitializeComponent() routine, but why it is taking sooo long?

Am I doing something wrong?
 
I have a form containing a lot of various forms objects (about
120-150). It takes about 10 minutes for the solution to load (only one
project). If I modify the corresponding .h file and return to the
[Design] tab the IDE become unresponsive to about 5-10 minutes again.
Click to expand...

Please check: http://support.microsoft.com/?id=832138 . It has a
solution for your problem.

Thanks,
 
Steve said:
Hi,

I have a form containing a lot of various forms objects (about 120-150). It
takes about 10 minutes for the solution to load (only one project). If I
modify the corresponding .h file and return to the [Design] tab the IDE
become unresponsive to about 5-10 minutes again. For example, if I double
click on a label, the .h code window appears with the corresponding event
handling function for 'Click'. If I delete that function and then return to
the [Deisgn] tab, it takes, and I just tested this, 12 minutes before VS2003
IDE becomes reponsive again and actually shows the Design window. Its obvious
that when I deleted the event hanlding function, VS2003 needed to remove the
corresponding '.. new System::EventHandler ..' line located in the
InitializeComponent() routine, but why it is taking sooo long?

Am I doing something wrong?
Click to expand...

Hi Steve,

Call product support services. We ahve a QFE available that fixs this
issue in all the cases we have seen. You can only get that QFE by
calling product support. The incident is free.

Ronald Laeremans
Visual C++ team
 
Please check: http://support.microsoft.com/?id=832138 . It has a
solution for your problem.

Thanks,
Click to expand...

Tarek,

Thank you for the link. However, it states that I must call Microsoft
Product Support Services in order to obtain the fix, and I do not have the
version of Vcpkg.dll that is listed on the Hot Fix page.

It lists:
7.10.3337.0

I have:
7.10.3077.0

Without the correct or later version, it does not seem as if I can get the
hot fix without paying the $245 dollars for a support call. "In special
cases, charges that are ordinarily incurred for support calls may be canceled
if a Microsoft Support Professional determines that a specific update will
resolve your problem. The usual support costs will apply to additional
support questions and issues that do not qualify for the specific update in
question. The English version of this hotfix has the file attributes (or
later) that are listed in the following table."

It makes no sense for me to pay $250 dollars to fix Microsoft's mistake! How
else can I resolve this issue, or, how can I be guaranteed that I will not be
charged?

Thanks.
 
It makes no sense for me to pay $250 dollars to fix Microsoft's
mistake! How else can I resolve this issue, or, how can I be
guaranteed that I will not be charged?
Click to expand...

Microsoft Support will never charge you if you call with an issue that
is turns out to be a real bug. In this case, we are positive that this
is a real bug. We also have a fix for it. You can call support without
any worries of them charging you for this incident.

Thanks,
 
Steve said:
Tarek,

Thank you for the link. However, it states that I must call Microsoft
Product Support Services in order to obtain the fix, and I do not have the
version of Vcpkg.dll that is listed on the Hot Fix page.

It lists:
7.10.3337.0

I have:
7.10.3077.0

Without the correct or later version, it does not seem as if I can get the
hot fix without paying the $245 dollars for a support call. "In special
cases, charges that are ordinarily incurred for support calls may be canceled
if a Microsoft Support Professional determines that a specific update will
resolve your problem. The usual support costs will apply to additional
support questions and issues that do not qualify for the specific update in
question. The English version of this hotfix has the file attributes (or
later) that are listed in the following table."

It makes no sense for me to pay $250 dollars to fix Microsoft's mistake! How
else can I resolve this issue, or, how can I be guaranteed that I will not be
charged?

Thanks.
Click to expand...

Hi Steve,

You have my personal guarantee that you will not be charged or the
charge will be reversed (if the call is only about this issue). If you
have issues on that with the support engineer you are talking to you can
refer them to me (my alias is the obvious unmangling of my posting alias
here). But that has _never_ been neccesary yet in a large number of
customers who have called to get this and other QFEs. We have a really
great support team that goes out of their way to help our customers. And
I do know most of them personally.

Ronald Laeremans
Group Program Manager
Visual C++ team
 
Yes, there was no problem getting the hot fix. Sorry for being a little
paranoid, I'll be more trusting next time!

The lag is now down to about 45 seconds. Should this be considered "normal"
overhead for a form with a large number of objects on it? If so does VS2005
attempt to speed this up?

Thank you for your help.
 
The lag is now down to about 45 seconds. Should this be considered
"normal" overhead for a form with a large number of objects on it? If
so does VS2005 attempt to speed this up?
Click to expand...

We've improved it a little in VS2005. We're currently also evaluating
whether we need to do more work in that area before we ship.

Thanks,
 
maybe this is a silly question, but if the bugfix is available for free, why
isn't it available publicly?
wouldn't it be more sensible to let people download it without having to
call support?

Bruno.



Ronald Laeremans said:
Steve said:
Hi,

I have a form containing a lot of various forms objects (about 120-150).
It takes about 10 minutes for the solution to load (only one project). If
I modify the corresponding .h file and return to the [Design] tab the IDE
become unresponsive to about 5-10 minutes again. For example, if I double
click on a label, the .h code window appears with the corresponding event
handling function for 'Click'. If I delete that function and then return
to the [Deisgn] tab, it takes, and I just tested this, 12 minutes before
VS2003 IDE becomes reponsive again and actually shows the Design window.
Its obvious that when I deleted the event hanlding function, VS2003
needed to remove the corresponding '.. new System::EventHandler ..' line
located in the InitializeComponent() routine, but why it is taking sooo
long?

Am I doing something wrong?
Click to expand...

Hi Steve,

Call product support services. We ahve a QFE available that fixs this
issue in all the cases we have seen. You can only get that QFE by calling
product support. The incident is free.

Ronald Laeremans
Visual C++ team
Click to expand...
 
maybe this is a silly question, but if the bugfix is available for
free, why isn't it available publicly?
wouldn't it be more sensible to let people download it without having
to call support?
Click to expand...

Because the fix for this bug did not pass all the required automated
tests to make it a publicly available bug fix. Normally all bug fixes
that we make publicly available need to pass a certain level of quality
which this fix could not meet (for lots of technical reasons). As a
result, we recommend that people only download this fix if they are
experiencing the exact problem that is described, otherwise it will
cause them more harm than good.

I hope this helps explaining things a little :)

Thanks,
 
Thanks for the answer. it makes sense to do it like that.

this brings me to another question however: why doesn't microsoft release
any service packs anymore for VS? with VS6 there were regular updates, and i
am sure that you guys solves a lot of bugs since VS 2003 was released.
heaven knows that intellisense alone could use some fixing...
VS 2003 is out for 2 years and still no service pack.

Bruno.
 
Bruno van Dooren said:
Thanks for the answer. it makes sense to do it like that.

this brings me to another question however: why doesn't microsoft
release any service packs anymore for VS? with VS6 there were regular
updates, and i am sure that you guys solves a lot of bugs since VS
2003 was released.
heaven knows that intellisense alone could use some fixing...
VS 2003 is out for 2 years and still no service pack.

Bruno.
Click to expand...

They have obviously been too busy working on other products.

" Microsoft Delays Visual Studio 2005 Beta 2 "
http://www.pcworld.com/resource/article/0,aid,120013,pg,1,RSS,RSS,00.asp


Bo Persson
 
this brings me to another question however: why doesn't microsoft
release any service packs anymore for VS? with VS6 there were regular
updates, and i am sure that you guys solves a lot of bugs since VS
2003 was released. heaven knows that intellisense alone could use some
fixing... VS 2003 is out for 2 years and still no service pack.
Click to expand...

VS2002 service pack is out already. We're also working on VS2003 service
pack right now.

I agree with you that two years feels like a long time to go without
service packs. But that's an issue that I neither control nor am aware
of all aspects of, so I'd rather not try to justify it, speculate or
comment about it :) Maybe someone else who knows more about it would :)

Thanks,
 
Tarek Madkour said:
Yes. See this for an example:
http://support.microsoft.com/default.aspx?scid=kb;en-us;837234


Not for Visual Studio service packs :( In VS2005, the start page will
include a notification area for such important pieces of information.
Click to expand...

We've just been using MSVC for the last year or so, so
I didn't know how this worked. Coming from Borland land, it's nice
to have a list of bugs addressed. As for notification of the patch,
I imagine that it will be posted here when it's released.

Thanks.
 
We've just been using MSVC for the last year or so, so
I didn't know how this worked. Coming from Borland land, it's
nice to have a list of bugs addressed. As for notification of
the patch, I imagine that it will be posted here when it's
released.
Click to expand...

You'll find it very useful to develop the reflex of checking
http://msdn.microsoft.com/visualc regularly.

All the cool articles, whitepapers, updates, etc. get advertised
there.

Thanks,
 
Hi Ronald,

Thanks for your responses! I do have a concern of my own though (please
don't read the following as an attack, its more of a concern). The policy
reads:

""In special cases, charges that are ordinarily incurred for support calls
may be canceled
if a Microsoft Support Professional determines that a specific update will
resolve your problem."

My concerns are as follows. First, you have to call to find out if you
'qualify' for the special case, so you must BET $250 your problem can be
solved for free. Second, it specifically says you are only qualified if a
'SPECIFIC update' (meaning one that ALREADY exists) will solve your problem.
This implies to me if you find a NEW problem you still pay $250 for the
provilege of telling MS about their mistake. And third, does this mean you
will only help people who have CREDIT CARDS with $250 in their account?

It is just a cop out for MS (or any company) to respond something like
'well, we get so many calls we would have to charge more for the product if
we didn't charge for customer support'. Well, you can also reduce such costs
by making BUG-FREE SOFTWARE!!! But paying for customer support makes us pay
for the privilege of de-bugging your software. Finally, the policy says 'MAY
be canceled'. Why does a MS Support Specialist get to determine this, seeing
as how such a person is hardly a neutral party? How would you like it if the
customer got to determine if he MAY pay for customer service according to
his 'support specialists' (ie., himself?). Oh, that doesn't sound good to
you? Neither does a MS employee deciding if a customer is going to have to
pay MS. You need a neutral party here...

I think if MS is going to CHARGE for customer support, they should have to
PAY people who find new bugs (say, $5000?)! What, that doesn't sound
reasonable from MS's point of view? Neither does paying for customer support
from a CUSTOMER'S point of view. After all, if we have to pay when we
mistakenly call you up with a problem that happens to be not be general bug,
why shouldn't MS have to pay for mistakenly putting a bug in their software?
You guys are aware most people will go DAYS of trying to solve such a bug
themselves before finally coming to the conclusion it might be an MS bug,
right? Who compensates such a person for this time, as if it truly does
result in the discovery of a new bug? I'm sure you pay for internal QA, so
why do you charge for external QA? In such a case MS is responsible for the
person's down time (which can be VERY costly to such a person), and it does
result in MS having a better product if a bug is truly revealed. So $5000 is
almost cheap...

I have always felt charging ANYTHING for customer support is dangerous and
bad business. It actually rewards companies for their mistakes, and thereby
makes it (sub-consciously) 'better' to actually have bugs!

At the VERY LEAST MS should set up a page to report bugs without having to
use a phone! When a customer reports a potential bug in your software he
shouldn't have to pay for a phone call (I only use a cellular phone like
many others so the 'free' aspect to the 800 line is of no help) or wait on
the phone to talk to someone.

And when do the charges for calling paid custom support get billed? BEFORE
or AFTER the phone call? If its BILL first and ask questions later, then I
believe it would be stupid to report a bug to MS that one finds in their
software (since there might be a charge of $250 if there isn't already a fix
for it, and there might be a charge even if there IS a fix for it), which
harms MS and me and everybody else. And heaven help the good samaritan who
tries to report something that turns out to not be a bug...

My 2 cents...

[==Peteroid==]

PS - I think the fact this thread exists at all is evidence that this
'paranoia' in regards to calling MS Customer Support is an issue that needs
to be dealt with...
 
Back
Top