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
  • Actually managed solutions and native solutions work in the same manner. Different projects within a solution are not related to each other unless you create a dependency from one to the other.
    In managed code you can add a dependency on another project by adding a reference to that project in the references folder.

    In native code you add a dependency to another project on the Dependency tab of the Solution Property page.

    When these dependencies are in place the dependent projects will always be built first, if required, whenever the main project is started for debugging.
Reply
  • Actually managed solutions and native solutions work in the same manner. Different projects within a solution are not related to each other unless you create a dependency from one to the other.
    In managed code you can add a dependency on another project by adding a reference to that project in the references folder.

    In native code you add a dependency to another project on the Dependency tab of the Solution Property page.

    When these dependencies are in place the dependent projects will always be built first, if required, whenever the main project is started for debugging.
Children
No Data