Sean

I have been successful with multiple projects all targeting micro framework devices. The trick is selecting which to deploy, and which is the default project when you are debugging.

So - for example, here is a solution I have with a bunch of projects in it. The trick is to deploy only one of them - otherwise, they stomp on each other. To choose what gets built and what gets deployed, you use the Configuration Manager - which is accessible a couple of ways: From the Build... menu, and from the little "Dubug" drop-down on the toolbar. Here is a screen shot of mine:


Here you can see all the projects - but only PWM1 will get built and deployed to my Netduino.

The second trick, if you have multiple projects and you want to step into code, you must select the startup project. To do that, you right-click on the project in the Solution Explorer, and select "Set as Startup Project". Then, when you debug, and set a break point, it will start the project you expect Here is a screen shot of mine. Here you see the PWM1 project is in bold, because it is the Startup Project.


Hope that helps.

- Sean

Mine was in a different place all together. The way to find out where Visual Studio is looking, Click Tools/Options, select "Projects and Solutions". On the left side of the options dialog box, and look (on the right side) at the value for "User project templates location". I copied the whole "Micro Framework" folder (which contained the NetduinoApplication.zip file) from the installed incorrect location to the folder specified on my options screen, and finally I was able to create a Netduino Application. Yay! Now I have Blinky working. Next step: Figure out how to stop the blinking ... Hmmm ....