Visual Studio 2005 Beta 2
Working with beta 2 of Whidbey (Visual Studio 2005) has been difficult so far, surprisingly difficult given how comfortable I had become at developing Windows.Forms based applications with beta 1.
I went back to my notes from the time I started using beta 1 of Whidbey to remember how many problems I had to learn to live with. Like many things, familiarity breeds comfort.
Among the problems I’ve had are:
·
Enabling break when an exception is thrown from C++ or Win32
caused an InvalidDeploymentException to be thrown when accessing simple
Properties.Settings.Default properties during application startup. The problem
disappeared when I cleared the DebugàExceptions
checkboxes, but not before spending several hours trying to work around the
exception. And now I’m hitting a vanished XML serialization assembly.
See http://www.dotnet247.com/247reference/msgs/42/211509.aspx
· Source code coloring in the editor keeps going away for some of my source files. If I cut and paste the contents between source files it comes back. But only to disappear again if I reload the project. The code compiles and runs without trouble.
· The GUI for defining settings under the application properties editor doesn’t allow settings to be declared from user types. By following the example created by converting a beta 1 application, I was able to manually edit the xml files to cause the type to appear in the list of choices.
· There are enough changes to the Windows.Forms controls and the designer generated code that it is often easier to recreate a Windows.Forms class from scratch using the beta 1 file as a reference than it is to modify the beta 1 file to be compatible with beta 2.