.NET4ever – the Swedish launch event for Visual Studio 2010
My friend Tiberiu Covaki (a.k.a. Tibi) just arranged a very nice launch event for Visual Studio 2010 in Stockholm under the banner .NET4ever. Besides introducing Visual Studio 2010 the speakers talked about WCF and WF, Silverligt, Entity Framework and F# (all of them 4.0 of course).
Tibi presented a lot of new features in Visual Studio 2010, some of which were new to me:
- Corrupted State Exception (link) will be removed from the usual stack of structured exception handling since it has to do with problems in the .Net framework itself.
- Power commands for VS that allows you to open a command prompt + browse directly to a subfolder.
- IntelliSense is improved so that you can type a part of a method name. E.g. if you type “range” after a List<> instance and it will find AddRange as illustrated below.
Alan Smith, a former colelague of mine, talked about WCF 4 and WF 4 as well as Windows AppFabric. He demonstrated the new more minimalistic configuration of WCF. He explained the difference between Windows AppFabric and Azure AppFabric, and then focused on how Windows AppFabric allows for monitoring and persisting workflows. He also gave a nice demo of a WCF Workflow service and Windows AppFabric.
Ted Malone also introduced some new “No repro” features in VS2010. Sadly I missed out on that presentation but Ted was gracious enough to fill in some of my gaps. The most interesting part is called IntelliTrace. IntelliTrace is an advanced code profiler that allows you to do historical debugging. Testers can record not only their actions and application state, but also all the environmental settings. If testers use virtualization then they can attach a snapshot of that virtual machine to their bug report. Developers can then use all this information to reproduce bugs in their development environments (read VS2010). Considering that there may be a lot of information and code being run developers can filter out things, e.g. only work with code that uses ADO.Net. According to Ted it would be possible to attach IntelliTrace to a production environment to monitor real production failures, but IntelliTrace uses a lot of resources so that will affect performance.