COBOL Compiler for .NET

For NetCOBOL for .NET V8, since Microsoft has not yet provided the shell addition, you would need to have your own version of Visual Studio 2017 (up until the point where Microsoft makes the shell interface available and it can be added into NetCOBOL V8). For earlier versions, no. Visual Studio 2010 through 2015 Shell is included with NetCOBOL for .NET. Only if you want features, or other development languages, that are not in the shell edition would you need to purchase Visual Studio from Microsoft. See the Visual Studio Product Line Overview.

The requirements are essentially those required by Visual Studio, with an additional 70MB of disk space for the NetCOBOL for .NET product. See the information on System Requirements on the Microsoft Visual Studio Standard page.

Applications can be executed on Microsoft Windows 10, Windows 7, Vista, XP and Server 2003/2008/2012. When you create the package to deploy your application, you will need to consider if the end-user’s machine will already have the .NET Framework installed. If not, you may need to include the appropriate parts in your package. The hardware and software requirements for executing applications is therefore primarily dependent on those of the .NET Framework. See System Requirements for Installing .NET Framework 3.5 for details of .NET Framework requirements.

Many common installer development environments have support that makes it easy to deploy .NET applications. NetCOBOL for .NET also includes a set of redistributable components that constitute the COBOL language runtime necessary for your applications to run on a client machine.

NetCOBOL for .NET comes in two editions: Enterprise and Universal. Enterprise focuses on creating applications for .NET. Universal combines NetCOBOL for .NET Enterprise with NetCOBOL for Windows Enterprise – so you are able to create applications for both .NET and native Windows.

No. The manuals are provided either as compiled help files or PDF files accessed from the Fujitsu NetCOBOL for .NET V4.1 program group or from within Visual Studio.

Yes – particularly if you are wanting to migrate existing ASCII (or ANSI Code Page, ACP) data or share data with ASCII/ACP applications. The User’s Guide provided with NetCOBOL for .NET fully describes the issues involved and required actions.

Not at all. NetCOBOL for .NET allows you to compile non-OO COBOL programs and execute these in the Common Language Runtime (CLR). However, if you want to communicate with .NET programs written in other languages, or take advantage of the support provided in .NET Framework classes, it will be necessary to understand a number of OO concepts and how they are supported in NetCOBOL for .NET. When compiling non-OO COBOL programs, for example when using NetCOBOL for .NET as part of a COBOL migration solution, the NetCOBOL system packages your standard COBOL program in this OO environment as a static method, called “Procedure,” of a class with your program’s PROGRAM-ID name. This means that you can call a traditional COBOL program in an OO manner, using the PROGRAM-ID as the class name and “Procedure” as the method name.

Yes you can. There are a few limitations in NetCOBOL for .NET that may prevent certain modules from compiling successfully. These limitations are listed in the NetCOBOL for .NET User Guide. Where the limitations are in areas that must be retained in your application, you can compile those modules with the NetCOBOL for Windows product and invoke them from the .NET code.

Use Windows Forms within the .NET environment. Windows Forms is a model for developing rich client GUI applications that are built around classes in the .NET Framework class library’s System.Windows.Forms namespace. They have a programming model all of their own that is cleaner, more robust, and more consistent than models based on the Win32 API or MFC, and they run in the managed environment of the .NET Common Language Runtime (CLR). NetCOBOL for .NET provides designer support making it easy to design your graphical interfaces and write the supporting COBOL code.

No. For now PowerCOBOL applications will continue as native Windows applications.

Yes they are – in a slightly different manner from traditional Windows applications. Traditional Windows-based applications process WM_COMMAND and WM_NOTIFY messages using special Windows Forms process events. In C# and in other languages (COBOL included) that support the .NET Common Language Runtime (CLR), events are first-class type members on par with methods, fields, and properties.

Yes. Support for COBOL’s sort/merge module was added in the V2.0 release.

By default – no. That is, if you are using the default character set modes of working with both NetCOBOL for .NET and NetCOBOL for Windows, and you are using the same file systems (e.g. NetCOBOL file system in both or Btrieve file system in both), then the files are compatible. Differences will only occur if programs are compiled to use different character sets or different file systems. For example, a program compiled with RCS(UTF8-UCS2) with NetCOBOL for .NET will store alphanumeric data using UTF-8 which would typically not be compatible with data in a file written using a program compiled with RCS(ACP) which uses ASCII data. If you decide to use different character sets in different programs, functions are provided so that you can convert the data between the character sets.

Currently we have only tested V6 thru V11, since these are the versions that have been available and supported during NetCOBOL for .NET’s life. Earlier versions should also work, but there is no guarantee. To ensure proper usage of the modules we recommend using the DLLs of the latest release of NetCOBOL for Windows.

The Common Language Runtime (CLR) defines a set of built-in data types that can be passed between languages. These data types are: boolean, byte, char, date, decimal, double, enum, single, int16, int32, int64, object, and string. Programmers can also create user-defined classes that can be passed between languages.

Yes, both DLL’s and COM objects may be referenced from within the .NET environment.

NetCOBOL for .NET supports: sequential, line sequential, relative, and indexed file access; EXEC SQL (Embedded SQL) via ADO.NET or ODBC. With NeoData VSAM files can be converted to SQL Server databases while the COBOL code remains unchanged – accessing and updating the data using COBOL file I/O statements.

Yes, you need to use the object-oriented extensions of NetCOBOL for .NET.

The following are limitations in this version:

• The SCREEN SECTION is not supported. Your NetCOBOL for .NET applications should use Windows Forms or Web Forms for interfacing with your users.
• The COBOL REPORT WRITER module is not supported.
• TYPEDEF STRONG is not supported.
• ENTRY statements are not supported. Code that relies on ENTRY points should be restructured so that each separate ENTRY point becomes a method.
• ALTER statements are not supported. ALTER was declared obsolete in the 1985 COBOL standard.
• A GO TO statement without a procedure name (used as the target of an ALTER statement) is not supported.
• The “STOP literal” statement, which would display a message to an operator and pause execution pending a response, is not supported.

Yes. Support for PowerFORM was added with the V2 release of NetCOBOL for .NET. PowerFORM was also added to the NetCOBOL for .NET product with the V4 release.