Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio
All postings are provided AS IS
with no warranties, and confer no rights. Additionally, views expressed
herein are my own and not those of my employer, Microsoft.
Microsoft has created what I think is a really cool mechanism for customers to report bugs and suggestions for our products - the Product Feedback center. Right now, you can report bugs in Visual Studio 2005 and the .NET Framework 2.0 via this website. The bugs from this site are transformed into the correct format and then reported directly into the same database that VS and .NET Framework product teams use to report bugs against daily builds of the products as they are being developed. There is also a really nice process put in place by the Developer Division community team (Josh Ledgard, et al) that ensures that bugs reported via the Product Feedback center are given special attention so they do not end up swept under the rug due to the lack of a repro in our test lab, and so they are all responded to in a timely (and hopefully professional) manner.
The Product Feedback site has increased the volume of bugs reported for VS and the .NET Framework, and in particular for setup (because setup is the first thing every customer sees in the product and because every customer must get through setup in order to use the product).
I posted this article that describes the steps that we recommend everyone follow when reporting a bug in setup for the various versions of Visual Studio and the .NET Framework. Included in this article are links to full lists of log files that are created by setup for each version of VS and the .NET Framework. I'll put those links here too to make them a little more visible:
I strongly encourage anyone who encounters a problem while installing or using VS or the .NET Framework and anyone who has a suggestion for how we can improve in the future to use the Product Feedback site. If your problem appears setup-related, please take a quick look at this article and include the requested information in your bug report if possible (but don't skip reporting the bug because you can't find a log file or something like that).
For those of you who have already used the Product Feedback site, thank you very much!
I found one bug in VS 2010 where to report that
Hi Pradeep Bora - The location for the Visual Studio bug reporting site moved in the time since I wrote this blog post. You can find it at connect.microsoft.com/VisualStudio nowadays. Sorry about that.
I started using Visual Studio 2010 (Vb.Net) about 2 years ago to replace one of my old VB6 program. I am writing an engineering program that involved simple graphic display. As I progressed I realized that the new program responded much slower than my older VB program. One of which was the speed in changing forms. The other was the control key response.This was particularly so where the control key encapsulates a timer. It took about a second or longer before the control key vanishes after clicking. Most disappointing of all was the graphic (line) display. I could literally see the lines being drawn on the screen instead of instant display. Worst of all when I zoom in or out (with my zoom sub-program using timer) its flashed at each zoom interval and at times I could also see the lines being drawn.
I have not encounter all the above using VB6. VB6 was SIMPLY perfect in every way!!
Please help look into this problem.
I have stopped continuing my program writing and have pondered as to whether I should use other programming language like C# to avoid this problem.
Hi Wong Chiang Heng - This type of question about VB is outside of my areas of expertise. I'd suggest posting a question on the VB forums at social.msdn.microsoft.com/.../home to get more help with this scenario.