I am actually working on a set of demos for TechEd next week (I know these demos should be finished now!, but I'm sure I will get everything up and running by the end of this week ;-)).
I struggled a couple of hours on a problem: I generated a SDK for a Windows Embedded CE 6.0 image using the Platform Builder 6.0 Plug-in in Visual Studio 2005. I then tried to install that SDK in order to use it in Visual Studio 2008 to develop a Smart device application for my device (I know you can develop your application into Visual Studio 2005, but I am kind of a geek and I like to use the latest tools...). The problem was that the newly installed SDK didn't show up in Visual Studio 2008... After a long investigation, I found out this is a known issue. The workaround to get the SDK showing up in Visual Studio 2008 is to select "custom" installation mode during the installation wizard and to deselect the documentation installation. I guess this will be fixed in a next release!
Back to writing code for my demos.... :-)
Have a similar problem. Kit from Logicpd for OMAP35x, comes with Windows Embedded CE 6.0 (+R2), but that won't install because it only want VS 2005, I also prefer to use the lastest tools, have VS 2008 now. Don't really want to revert.
Or does VS 2008 embody everything one needs already?
I will try the workaround you suggest, and post the outcome.
Otherwise, any advice gratefully received.
You probably are talking about Platform Builder 6 which is the tool that enables developing Windows Embedded CE images, right?
PB 6 is a plug-in to Visual Studio 2005 only, not to Visual Studio 2008.
What I was talking about in my post was the SDK (Software Development Kit) that enables developing applications for a specific Windows Embedded CE 6 image (previously built using VS2005 and PB6).
Let me explain what the process is to develop images and applications for Windows Embedded CE 6.0.
First step is to build an image using VS 2005 and the Plugin Platform Builder 6.0. You will be relying on what we call a Board Support Package (BSP) provided by the OEM of the board you want to build an image for and that contains all the low layers and drivers necessary to make CE run on the board. Within VS 2005 + PB 6.0, you will select the features you want for your OS. You will then build the image, deploy it to the target and debug it. Once the image is up and running, you will export an SDK using PB for your specific image (containing the exact APIs your OS image is providing). This SDK will be installed on a dev platform running VS 2005 or VS 2008 and you will be able to develop applications for your CE image.
Note that you could develop native applications using Platform Builder (at the same time you are developping the OS image), but if you want to develop .Net applications or to separate kernel and applications development, you would rather go for the process described below.
Hope this calrifies things :-)
Enjoy developing for CE 6.0
Is there anything new about that issue? (installed CE SDK not displayed in Visual Studio 2008)
Not for the moment Peter.
As soon as find out more about it, I will update the post.
So are there any plans to support the Platform Builder 6.0 plug-in in Visual Studio 2008? I can't believe Microsoft wouldn't provide support for using their latest CE tools with their latest IDE.
I can't tell you about the plans for a support of the PB 6 plug-in into Visual Studio 9 (a.k.a. VS 2008). What is sure is that you are right saying we can't afford not supporting the latest toolsets.
We are seriously considering the different options as this is a feedback we are getting more and more from our customers and we will provide updates as soon as our plans are clearer. I will post on this for sure when the moment comes!
Thank you for this feedback!
Seriously PLEASE support this. Having a virtual machine with vs2005 and pbuilder installed is my interim solution, since both don't play nice on the
Thank you, I've tried to install without the documentation, but it still doesn't show on the list...
Did you uninstall any previously installed version of the SDK?
Wait a minute..Im confused.
With the introduction of .NET CF, how does it change the picture?
With the introduction of Embedded CE OS provided by microsoft, does that means that the OEM no longer build any custom os image? I'm confused by all the options. Can someone please clarify?
Don't be confused Edwin!
Windows Embedded CE provided to OEM as a tool set enabling them to build custom OSes is and will still be there. I would even say more than ever!
The .Net Compact Framework is an application framework abstracting the OS and the Hardware that is available as a component in the CE catalog.
When developping a CE 6 OS, you use Visual Studio 2005 and the plug-in called Platform Builder 6 to select the OS features you want to have in your custom OS, develop your own drivers and customize the whole.
Then to develop applications that will run on this customized OS, you will use Visual Studio 2005 OR Visual Studio 2008. If the applications you want to develop are native applications, you will use a SDK that you would have generated using Platform Builder. If the application you are developing is managed, then you will develop on top of the Compact Framework (version 2.0 or 3.5), so there is no need for an SDK as the CF is the same from one target to another one.
Does this make sense and answer your questions?
Any news on Microsoft's plans to support the Platform Builder 6.0 plug-in in Visual Studio 2008?
There will be no support for PB6 in Visual Studio 2008 as far as I know.
It seems this issue still exists, even after I remove the custom Windows CE 6 SDK and reinstaill it with Documentation de-selected, and then reboot my machine. It still not in the SDK list of Visual Studio 2008. But this new CE 6 SDK does appear in the SDK list of Visual Studio 2005. And I had no problem with Windows Mobile 5 or 6 SDKs in working with Visual Studio 2008.
Any other clues?
I guess you have tried multiple times and ways of doing. I would say the right order would be to uninstall previous version, reboot, install the SDK with documentation deselected and then check in VS 2k8.
If this doesn't work I can try to put you in touch with some dev guy.