Is there some way to report a MAJOR BUG with Visual Studio.NET to Microssoft

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

Guest

I'm at the end of my rope. We have an important project that is being
totally whacked by an inexplicable bug with the Visual Studio.NET WinForms
designer. It seems that no matter what we do, forms and controls in multiple
projects are being randomly resized whenever we do a save or build,
rendering them virutally unusable.

As far as I am concerned THERE IS NOT EXCUSE for a bug like this in the
designer and I have been unable to locate the source of the problem. Someone
did report seeing this problem when he changed the default font within a
form, but that turned out to not be the case with us.

Numerous posts on this have gone unanswered and searches of every type for
the cause/solution have yielded nothing.

Again, SIMPLY SAVING A FORM SHOULD NOT ALTER ITS LAYOUT!!!!

What gives???
 
It sounds like it's worth $245 to you to get peice of mind, use a paid (or free
if you are a memember) MSDN support incident.

http://msdn.microsoft.com/subscriptions/support/default.asp
800-759-5474

Or you could post a zipped solution with reproduiction instructions, and we can
try to save you some money. Cheer up, it's highly unlikely you won't find a good
answer between MS and this newsgroup. If your questions have been unanswered, I
promise I'll take a look right away.

Bob
 
It sounds like it's worth $245 to you to get peice of mind, use a paid (or
free
if you are a memember) MSDN support incident.
Click to expand...

Plus, if it turns out to truly be a bug on Microsoft's part, then I don't
believe they charge you for the incident.
 
I want to publicly thank MS for stepping up to the plate and volunteering to
help here.

As it turns out, we did find a workaround that solved the problem, but it
does appear to be a rather odd and frustrating bug.

Size properties in the designer generated source code were being
mysteriously altered whenever we would did a save (including doing a build
that resulted in an implicit save). The alteration was to SOURCE code (not
compiled code), which made no sense whatsoever.

In fact, it was maddening and put us back by several days trying to solve
the problem.

We finally stumbled upon a solution that took care of it (although we have
no idea why):

On inherited child forms, whenever we used the default of the form below we
would have the problem:

public class AgencyManagementView :
MyCompany.Application.Common.BaseChildFormView{etc}

Replacing the above with something like the following pattern solves the
random auto-resizing of forms and controls on save (although , again, it
makes NO sense as to why):

using MyCompany.Application.Common
public class AgencyManagmentView : BaseChildFormView{etc}
 
I want to publicly thank MS for stepping up to the plate and volunteering to
help here.

As it turns out, we did find a workaround that solved the problem, but it
does appear to be a rather odd and frustrating bug.

Size properties in the designer generated source code were being
mysteriously altered whenever we would did a save (including doing a build
that resulted in an implicit save). The alteration was to SOURCE code (not
compiled code), which made no sense whatsoever.

In fact, it was maddening and put us back by several days trying to solve
the problem.

We finally stumbled upon a solution that took care of it (although we have
no idea why):

On inherited child forms, whenever we used the default of the form below we
would have the problem:

public class AgencyManagementView :
MyCompany.Application.Common.BaseChildFormView{etc}

Replacing the above with something like the following pattern solves the
random auto-resizing of forms and controls on save (although , again, it
makes NO sense as to why):

using MyCompany.Application.Common
public class AgencyManagmentView : BaseChildFormView{etc}
 
Back
Top