Using Net Express project import wizard for Visual COBOL 2.1 questions

After the import, the imported project directives are listed in the Additional Directives box on the project properties screen.  We would also like to add USE"..\MYDIRECTIVES.DIR"  to the list of additional directives.  Our Net Express projects don't always have the same directives but there are certain directives we've had to add to our Visual COBOL projects so they will build without errors (for example, REMOVE"OBJECT-REFERENCE") and we list these in MYDIRECTIVES.DIR.  Can we do this or will the compiler only use the directives in MYDIRECTIVES.DIR ?

We are bringing about 350 projects from NX 5.1 to Visual COBOL and we want to maintain two sets or source, the original, unmodified NX source and the Visual COBOL source which we will modify.  In the import wizard, we specified a different directory (from the NX directory) for the Visual COBOL project but the source was not copied to it.  Also, each time we use the wizard it creates a solution along with the imported project but we want to import multiple projects into a single solution.  Our solution to this is to copy our entire Net Express project to a temporary directory and then import the NX project from it.  We then copy, in Windows Explorer, the project's folders and files to our application's solution folder and select Add ... Existing Project in Solution Explorer and add the copied project.  This doesn't take long but let us know if there is a quicker way to do it.

Tags:

Parents
  • Verified Answer

    The original idea was that this _Shared project was there to contain files, directives etc that are shared between the projects in a solution, which may well be the case in future and was the reason for the name that was choosen.

    The reason that it exists even when there are no files in it is because of how the Visual Studio project upgrade mechanism that we are now using in 2.1 returns the name of the project to be opened.

    It was necessary to create this extra project in order for the real project to be set as the Startup project.

    As you point out, it is currently unnecessary and can be removed from the build.

Reply
  • Verified Answer

    The original idea was that this _Shared project was there to contain files, directives etc that are shared between the projects in a solution, which may well be the case in future and was the reason for the name that was choosen.

    The reason that it exists even when there are no files in it is because of how the Visual Studio project upgrade mechanism that we are now using in 2.1 returns the name of the project to be opened.

    It was necessary to create this extra project in order for the real project to be set as the Startup project.

    As you point out, it is currently unnecessary and can be removed from the build.

Children
No Data