Skip to main content

Build Tool for Windows with CICS (and SQL)

  • June 26, 2019
  • 2 replies
  • 0 views

I have been tasked with building an online system consisting of about 200-300 programs/screens which use CICS to handle the UI.  The backend is Microsoft Server.  We are upgrading from NetExpress to Enterprise Developer 4.0.  What do I have to do to get the compile working with the build tool.  The programs compile just fine with Visual Studio 2017 with a developer license - but the build needs to be a separate process.  It actually will be launched from MSBuild as a remote server.  Can it be done? 


#EnterpriseDeveloper

2 replies

I have been tasked with building an online system consisting of about 200-300 programs/screens which use CICS to handle the UI.  The backend is Microsoft Server.  We are upgrading from NetExpress to Enterprise Developer 4.0.  What do I have to do to get the compile working with the build tool.  The programs compile just fine with Visual Studio 2017 with a developer license - but the build needs to be a separate process.  It actually will be launched from MSBuild as a remote server.  Can it be done? 


#EnterpriseDeveloper

I don't entirely understand your question. Could you provide a more detailed example of what you're trying to do?

You can build Visual Studio solutions and projects from the command line using Microsoft's msbuild utility. This works for COBOL projects just like any other language.

The system running the build will need Visual Studio and Enterprise Developer (or Visual COBOL, if ED-specific features aren't required).


  • 0 replies
  • July 3, 2019

I don't entirely understand your question. Could you provide a more detailed example of what you're trying to do?

You can build Visual Studio solutions and projects from the command line using Microsoft's msbuild utility. This works for COBOL projects just like any other language.

The system running the build will need Visual Studio and Enterprise Developer (or Visual COBOL, if ED-specific features aren't required).

I am closing this because I discovered that if I execute MSBuild from a Visual Studio developer prompt all the directives i.e. CICS and SQL are set

OK to close