By now everyone knows that Visual Studio 2008 has launched, along with the .NET Framework 3.5. This version, previously known as 'Orcas', brings some significant new capabilities with it.
But first things first, installation and out of the box impressions.
I installed 2008 on a system that was clean in the sense that it had never had any of the pre-release versions of Orcas installed on it. I used the Virtual Machines that Microsoft provided to play with the pre-release versions. Wonderful idea judging by all the recent blog posts on how to uninstall the beta's before installing the final release.
If you do need help uninstalling the beta's in order to get the final production version installed, ScottGu has an excellent post on the topic.
Microsoft's official 2008 site has a great deal of good information, tutorials and other examples to peruse, I strongly recommend you check it out.
Anyway, I installed, from a DVD image I burned from the ISO file I downloaded from MSDN. I installed the Professional edition as I do not have access to a Team Foundation Server.
Installation was NOT smooth, the install kept crashing trying to install the .NET Framework 3.5 which was one of the very first steps. So I tried downloading and installing the Framework directly, which also failed.
Looking at the log files I was surprised to see that it was complaining that the 3.0 Framework SP1 was not present and that 3.5 considered that a pre-requisite for installation. Since I was running Vista which came with 3.0 pre-installed I was surprised as I check Microsoft Update weekly and I was sure the SP1 patch had already been installed.
I finally rebooted and logged in as Administrator and re-installed the standalone version of 3.5 again, this time it worked fine. Then I installed 2008 still logged in as Administrator and again everything went fine. The install, including the new MSDN library took slightly over 2 hours.
Once everything was installed I fired up the IDE which took another 10 minutes to configure itself based on my environment selections. Once it was finally up I was able to begin playing around a bit.
The IDE is very similar in appearance to 2005, in fact it is identical, at least initially. The first time I noticed a significant difference was when I opened a project. Visual Studio now uses the native file dialogs as opposed to it's own custom versions. (This is true on XP as well.)
This is a welcome change especially on Vista as it allows all the functionality of the file dialogs that Windows provides.
There are numerous changes under the hood of course, and many many changes and new features in the languages and Framework which I hope to touch on in a future post.
One other thing I noticed was the fact that Visual Studio now seemed to be a lot faster to load. This is of course a welcome change!
One of those buried features is very welcome and much talked about, multi-targeting! As you can see from the screen shot below this allows you to target an
application at the following frameworks:
2.0, 3.0 or 3.5
This means you can continue working on your 2.0 or 3.0 projects using the newer IDE. Rick Strahl has a great post on moving projects between 2005 and 2008 and back. Basically the project format has NOT changed, and the Solution file changes are minor. This means that you can work on 2.0 targeted applications in either 2005 or 2008 with no particular problems.
I was able to open several 2005 projects, work on them, compile them, run and debug them with no issues. I opened WinForms, ASP and Class library projects with no issues.
One annoyance I did notice was that the help library was much slower to open and seems prone to hanging. The MSDN library is fine when launched standalone, but when launched from within the IDE it is slow to actually show up.
More to come in the next post! Stay tuned.
Cheers,
Robert Porter