ETA on Smart Device Projects for Visual Studio 2010_问答_开发者

I really want to upgrade to Visual St开发者_运维问答udio 2010. But since I do a lot of development for the Pocket PC version of Windows Mobile I cannot. (I develop for a Symbol device that does not support Windows Phone 7, so that is not a option.)

Does any one know any kind of time frame of when Microsoft plans to add support for Smart Device Projects into Visual Studio 2010?

Update: Since this is looking less and less likely without intervention from the users, Please go here and vote for this feature.

Microsoft's current public statement says that, apart from Windows Phone 7 development, there will not be Smart Device Application Development added to Visual Studio 2010.

This obviously raises concerns and has implications for a lot of people, and there are more than a few of us lobbying Microsoft very hard to change that plan and to get them to include some sort of support for Smart Device programming outside of Windows Phone.

I'm hopeful, maybe even optimistic, that their stance will change and that we will get something - even if it's only CF 3.5 targeting actual hardware (i.e. no emulator support) - at some point down the road. Right now they've got all hands on deck trying to get Windows Phone out the door, and until that happens, I wouldn't expect much for resource allocation toward other device features.

So what does that actually mean? In my mind I wouldn't postpone installing VS2010 until they have device support. My guess is it won't happen until early next year at the absolute earliest and realistically I would say mid to late next year if it happens at all. Again, I'm optimistic that it will, but I'm also a realist, so I'm not going to base my business decisions and future on it happening.

Add your support to the following Microsoft Connect Item, it's had quite a bit of interest being the 3rd highest voted suggestion so far.

http://connect.microsoft.com/VisualStudio/feedback/details/595712/no-support-for-windows-ce-and-compact-framework-development-in-vs2010

Through private conversations I've had with the Customer Advocacy Team at MS it would appear that they are really digging their heels in over this. MS reneged on promises to include Smart Device Framework support in VS2010 early on in the product life cycle.

It is really frustrating because at some point the development tools will fragment and you'll end up with having to maintain separate development, source control and build systems for targeting Windows CE. Who is to say that the tools will even work on future versions of Windows either or even if they will live side by side with future versions of VS. Remember this lack of support also hurts people doing unmanaged code on CE too.

MS is doing a great job of remaining silent here, the silence is already causing people to look at alternative platforms. Without a statement of intent no business is going to invest in Windows CE development without knowing the future of the OS and the tools to develop on it.

All recent Visual Studio versions can be installed side by side. You could upgrade now for desktop development, then when smart device support is rolled out, migrate your projects to VS2010.

http://social.msdn.microsoft.com/Forums/en/setupprerelease/thread/fce95ec7-728d-41d1-ab13-74a2fd3a4136

I am forced to have two VS installations side by side. However, another issue - that is causing me more pain is that TFS 2010 doesn't work with VS 2008 - there is a plugin, of course, but there are many issues with it which make it unusable.

So to have source control, I have installed SVN on my machine.

Microsoft once again, has proven that they have no concern for the devs at all. Their tools don't work together, backward compatibility is not there, all of which makes their dev tools a big load of crap.

MS replied to that connect issue:

Hi folks,

In the first quarter of 2013, we plan to provide tooling for Visual Studio 2012 to create apps for Windows Embedded Compact v.Next. We’ll be announcing more details in September, including the roadmap for .NET CF. You can find more details this Fall in the Windows Embedded Compact website at http://www.windowsembedded.com.

thanks, Doug Turnure Visual Studio PM