9 replies to this topic

[Igor Kondrasovas]

Hello, I am using Visual Studio 2010 Ultimate to create my Netduino projects. I am using multiple projects in the same solution, as I usually do with other project types. However, I am experiencing strange behavior while deploying them. Even if I select a project as the default project in the solution, this project is not the one deployed to target. I still did not find any logic on how Visual Studio is choosing which project will be deployed, but it is usually the same project every time, until something (that I don´t know) happens and them another project is the one that is always deployed. Is anyone else with the same issue? Thank you, Igor.

[Stefan]

Hi Igor, When using multiple projects in a single solution, it'll normally deploy all projects and runs the StartUp project. This is very common behavior I suppose.

[Chris Walker]

Hi Igor, Also, if you go into the Solution's deployment properties, you can select/deselect which projects you want to deploy to your Netduino. Chris

[Stefan]

Also, if you go into the Solution's deployment properties, you can select/deselect which projects you want to deploy to your Netduino.

Yay, I reached my target for today, learned something new

[Igor Kondrasovas]

Hello Stefan, Thank you for the reply. Making a comparison to regular Windows Applications, if you have multiple Applications (.exe) projects in a solution, you will have started only the one marked as the "Startup Project". In my case (have a look on the attached screenshot) you have the "LAB1_AcionarLED" project set as startup and looking on the output log (in attach also) you see that "LAB3_AcionarBotaoRevisado" is actually deployed to the target. All projects in my solution are Netduino Projects, not class libraries or any other kind of project, so I believe that Visual Studio should be deploying only the one it is marked to be the start up project. What do you think? Thank you, Igor.

Attached Files

•  Capture1.PNG   174.85KB   17 downloads
•  log.txt   3.28KB   1 downloads

[Igor Kondrasovas]

Hi Igor,

Also, if you go into the Solution's deployment properties, you can select/deselect which projects you want to deploy to your Netduino.

Chris

Hi Chris,

I did know that screen! Thank you!

However, I really want to deploy a single project, the one I marked as startup project! But this is not what is happening (see my reply to Stefen).

What do you suggest?

Igor.

[Dan Morphis]

Hi Chris,

I did know that screen! Thank you!

However, I really want to deploy a single project, the one I marked as startup project! But this is not what is happening (see my reply to Stefen).

What do you suggest?

Igor.

Igor, an easier method than fighting with the config screen is to unload the projects you don't want deployed to the Netduino. That is the method I use.

-dan

[Igor Kondrasovas]

Igor, an easier method than fighting with the config screen is to unload the projects you don't want deployed to the Netduino. That is the method I use.

-dan

Hello Dan,


This is exactly what I am doing today. However, I would like to see if I am getting out of my mind or if there is someone else who is experiencing the same problem... do you have this problem?


Thank you,


Igor.

[Dan Morphis]

Hello Dan,


This is exactly what I am doing today. However, I would like to see if I am getting out of my mind or if there is someone else who is experiencing the same problem... do you have this problem?


Thank you,


Igor.

I do indeed. I wouldn't say so much that is is a defect as it is the way that netmf and VS work together. When VS is uploading the projects to the board, it expects that every project is needed. And its kind of a crap shoot as to which assembly gets picked as main.

Most of the time you won't have multiple non-related assemblies in a solution, so for most people its a non-issue.

-dan

[Igor Kondrasovas]

I do indeed. I wouldn't say so much that is is a defect as it is the way that netmf and VS work together. When VS is uploading the projects to the board, it expects that every project is needed. And its kind of a crap shoot as to which assembly gets picked as main.

Most of the time you won't have multiple non-related assemblies in a solution, so for most people its a non-issue.

-dan

Hello Dan,


I understand what you say about having multiple non-related projects in a solution, but I have to disagree in general:

If Visual Studio allows a "Set Startup Project" option while managing multiple Netduino projects, then I think this should work. So either you have the correct project deployed or Visual Studio should not enable this option to the user, since you will expect that it work. In other types of projects, like Desktop, Web, Mobile, you have have multiple "executable" projects in a single solution and the one you set as startup will be actually the one launch.

I know that working with project templates and integrating thing to Visual Studio should not be a piece of cake, but I can be pretty sure more people will have the same user experience I had.

I just openned a post on the .NET Micro Framework Forum that references this conversation: http://www.netmf.com...1c-c446951f1fc4

Regards,



Igor.