Visual Studio - build/debug/compile behavior, Native multi-project solutions vs. Managed multi-project solutions

Visual Studio 2013, Visual COBOL 2.2

Please confirm as to whether this is expected or default VS behavior or not.

Assume a Native solution with two projects and a Managed solution with two projects

It appears that Visual Studio behaves differently on Native multi-project solutions vs. Managed multi-project solutions in respect to the following:

When you click DEBUG at the top menu of VS and then choose either Start Debugging or Start Without Debugging ...

on a Native solution, it will build only the first project (program) (the one designated as the start-up-project) of say, a two-project (two-program) solution, before it starts it,

whereas on a Managed solution, it will build both projects (programs or classes) of say, a two-project solution, before it starts it.

On both the Native solution and the Managed solution, the Configuration Manager has Build checked for both projects of each solution.

Thanks,

Austin

Parents
  • Austin,

    In both managed and native projects Visual Studio will check that the startup project is up-to-date and rebuild if necessary, and will also build any dependencies. Do you, by any chance , have a reference to your second project from the first project in the managed case? If you do, that will explain why it is also being checked.

    Gael
Reply
  • Austin,

    In both managed and native projects Visual Studio will check that the startup project is up-to-date and rebuild if necessary, and will also build any dependencies. Do you, by any chance , have a reference to your second project from the first project in the managed case? If you do, that will explain why it is also being checked.

    Gael
Children
No Data