Bugs, bugs ...

  • Thread starter Thread starter PawelSokolowski
  • Start date Start date
P

PawelSokolowski

Hi all,

Is there any place where can I report bugs in Microsoft products in a way
that gives somethings ?
I mean anyone there cares ?
I was coping with bugs in Visual Studio for years, but I have enough.
After installing Service Pack 1 for .NET 2003 I just cannot stand it.
Simplest things are buggy like never before.

Examples., (those that I have never encountered without Service Pack)
1. Intellisense stops working after some declarations with comma separated
values.
2. Mouse cursor moves stopped marking blocks, although double clicked was
marking words propelly, started to work after restarting environment.
3. When I open some source file in the editor, and close it, I rarely get
the previous file on screen, usually I get some other file, and I am
thinking hard where I was and why I am here.
4. First day I installed it, after several minutes, main menu stopped
working, everything else worked, but menu was just like dead picture.

I hope they did not mess up the compiler

Of course there are some improvements, but still not the things that should
be done in first place.
Why code collapsing does not survive closing and opening the solution ?
When I do maintnainceof my thousands of code lines I am collapsing code that
I do not need to see. It clears the image, and helps to see what's
important.
Unfortunatelly is all gone when I close the file.

Regards
Pawe³ Soko³owski
 
there is more...

ComboBox that contains methods of currently edited class (below editor tabs,
on the right) started behaving strangely, it was opening down, but only
showing a one pixel wide black line instead of a window.
Restarting environment helped.

Regards
Pawel Sokolowski
 
PawelSokolowski said:
Big thanks !

Now I have the weekend for reporting all bugs I have found :)
Click to expand...

I find it's usually worth posting a short but complete program
demonstrating the program on newsgroups first, as a sort of
pre-validation step - if you've just misunderstood something (as
happens to us all from time to time) you're more likely to get good
feedback as to why it isn't a bug from newsgroup readers than from the
MS system.
 
PawelSokolowski said:
Big thanks !

Now I have the weekend for reporting all bugs I have found :)
Click to expand...

You can report there, but I guarantee you, it will be in general a
waste of time.

As Jon said, it's often better to post a repro in the newsgroups, so
people here can respond to it, provide workarounds (as you have to use
a workaround anyway, MS patches very slowly), and if necessary,
escalate (MVPs) to mailinglists with the product teams. I stopped
posting issues to Connect some time ago, as it's simply too frustrating
to read after a loooooooong period of time that some ms employee closes
an easy to reproduce issue as 'by design'.

FB

--
------------------------------------------------------------------------
Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
LLBLGen Pro website: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------
 
Frans,

In my opinion is what you write in two ways not true, first of all do you
take a little bit the writing style as Jon in my idea often does, from which
I often tell to Jon that at least I don't like it. (I hope that he sees now
what I mean with that). Secondly I get forever answer from connect.
Sometimes negative sometimes positive from my point of view.(I never tell
that I am MVP when I am reporting a bug using this method).

Jon gave two advices, which I both agree with him: first to send everything
documented well and secondly probably because it takes a long time to get
direct result to post the problem as well here (the latter just as I
understood it, not that he wrote that). In my idea suggest your message that
Jon is too telling that it is out of sense to report.

I have even done myself a suggestion this morning about the IDE, because in
this case I found that a better place than the product team..

Cor
 
Hello Pawel,

The bugs you are experiencing are not normally reproducable in everyone's
environment. MS did not release a tool that behaves this way for everyone.
What you are experiencing is probably not unique, however. This problem may
have been solved before.

You have the right to get product support for issues like this, depending on
how you purchased your product. I encourage you to seek out product support
services from MS.

--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik

Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
 
Back
Top