I have been eagerly anticipating the release of Visual Studio 2010 and the ..Net Framework 4.0 for a while. I even did some work with the betas and release candidates. Now that Visual Studio 2010 has released, I have been working on an adoption plan for my company, Black Blade Associates.
I was hoping to embrace Visual Studio 2010 quickly, but after some investigations it seems that we will need to take a much more conservative approach. Here are some reasons that I’ve found not to upgrade to Visual Studio 2010:
No InfoPath forms development support
It seems that the InfoPath integration first introduced with Visual Studio 2008 is gone in Visual Studio 2010. If you want to create an InfoPath form with custom code and manage the code in Team Foundation Server, you will need to flip between three different applications. Don’t take my word for it. Watch a video demonstration from the Microsoft product team. This seems like a crazy way to work.
Why do I care so much about it? We do a lot of workflow development for the SharePoint platform, and web-enabled InfoPath forms are a big part of that. The painful InfoPath forms development story in Visual Studio 2010 is a deal breaker for us.
No support for Windows Mobile 5, 6, 6.5
Visual Studio 2010 only supports developing Windows Phone 7 application development. Developers needing to create Windows Mobile 5, 6, or 6.5 applications will need to use Visual Studio 2008. This is not such a huge issue for me, but it would be a big problem for the large community of Windows Mobile developers needing to support the new Windows Phone 7 operating system while maintaining support for existing mobile operating systems.
Have you upgraded?
Have you found other reasons that prevent you from upgrading quickly to Visual Studio 2010? Post a comment. I’d love to keep a list of known upgrade impediments.