Quick Information - Windows to DotNet COBOL Migration.     

NetCOBOL For DotNet User's guide Documentation found in 
START,PROGRAMS,FUJITSU COBOL FOR .NET V4.x is a great reference.  


For the most part, every standard bit of COBOL will compile fine, migrating from
NetCOBOL for Windows to NetCOBOL for .NET.  You are moving from unmanaged code
to managed code, with the ability to take advantage of what .NET has to offer.

- Your environment changes.  You move from the Project Manager, to the Visual Studio
  Environment ( a much better environment ).  You can debug seamlessly through your
  mixed language environments.  (see the quick information on DotNet Debug, which points to help).

- Your compile options are new, 
  and where you set your library files, and copybook paths.
  It is all part of the Visual Studio environmnet.  Right clicking on the solutions/project, 
  then selecting "Properties" will get you a tabbed environment on your left where your settings
  are.  You can compile by the command line as well, or a tool is available at Mosersoft.COM
  who is a partner to help with the compiles (click and compile).
  Go to the guide mentioned above and search on Compile options.

- Screen Section.
  This is a text based interface, not graphical in nature, and not supported in the .NET version.
  There are a couple of different options.  Flexus.com (Alchemy Partner), provides a conversion
  for the screen Section.  You can also convert your screens into DotNet forms. Tools can help
  automate this process, and another partner (Mosersoft.Com) can help in that area.

- Calling Unmanaged Code 
  (Microsoft API's, VB6 DLLs', C DLL's (code built under a non dotnet enironment).
  You need to create an interface to these routines to call them.
  A couple of samples are available, and referring to PInvoke(Platform Invoke), in the 
  User's guide mentioned above is a big help.  Questions, or need something built, feel
  free to reach out to Support or one of the partners.