[Codeproject daily recommendation] vs. Net ide bugs & workarounds

Today, I went to the topic bugs & workarounds in codeproject and saw some bugs in Dev for "Quick Start". I am sympathetic to: (and Quick Start workaround, admire :)

Although I have not met most of them, I would like to brief you on repro and comment on it for your reference. This article is aboutVs. Net ide.

1.Intelliisense bug in vs. Net by Tom Welch
Vs. NET 2002?CodePoint arraypoints [] = {point (2, 3), point (5, 7), point (10, 5)}; this will cause the intelligent awareness of the Code in the IDE to fail. It should be out of date now. compilation fails. in my experience, SMART awareness fails only when the previous Code has syntax errors. Therefore, it is found that SMART awareness is ineffective, checking the Code has become one of my habits: Someone recommends visual assist for.. net.

2. Watch out for this web form designer issue by senkwe Chanda
Vs. NET 2003, web and Windows apps all have a problem: Adding Code before the Form class generated by the designer will make the designer unable to correctly identify and display the UI, I have encountered this many times, because the error message of IDE has already prompted that this class is the first class, and it is better to move the code I have added to the back or other places each time, unlike the author, the author is somewhat stubborn: After compilation, why can't designer be correctly identified? Everyone (especially Dev) high expectations for Microsoft: however, this problem has not been found in vs2005 after my experiment.

3. Visual Studio. NET blank property browser bug by Akash Kava
Vs. NET 2003, after adding some installation files, the project's attribute box does not show anything. I have never encountered it. The author said that I deleted it.C: \ Documents ents and Settings \ User \ Application Data \ Microsoft \ visualstudio \ 7.1A small plug-in is provided to automatically delete the folder every time vs. Net exits.

4. remedy for fatal error c1190 by Sylvester, ASIL Gerard
Vs. NET 2003, a fatal error c1190 occurs during the interaction of hosted and unmanaged code, never encountered (or don't want to encounter :). solution:<Projectname>. vcprojThe basicruntimechecks value in is set to "0"

5. dbgfix: an add-in to properly launch ie during ASP. NET debugging when running vs7 under alternate credentials by Rama Krishna Vavilala
Vs. NET 2003, this is cool. I used a well-known Dongdong detour to hijack API calls to correct the parameters of an API call, so that non-admin users can debug ASP. NET.ProgramIE is started but cannot be displayed. Specifically, it is the last parameter of CreateProcess.Startupinfo. Null should be passed in to ensure that the IE window of the new process and the original process belong to the same window StationWinsta0But vs. NET 2003 actually imports an empty string, so that the IE window of the new process does not belongWinsta0The user cannot see. Cool! Again, we proved that detour could make it easier for us to do some cool things. Like!