Micro Focus Studio Enterprise Edition for Windows > Programming > Managed COBOL Programming > Managed COBOL Programming > Code Page Conflicts in .NET Managed COBOL > Example of Code Page Conflicts in .NET Managed COBOL

Example of Code Page Conflicts in .NET Managed COBOL

Note: The following applies to .NET managed COBOL only.

Visual Studio creates partial classes in COBOL to give programmatic access to WPF and WCF user interfaces. These partial classes are auto-generated and can then be updated by you or Visual Studio.

In the following example:

Window1.xaml.cbl is the source code of a WPF (or WCF) user inteface.
CodePageStuff.Window1 is the partial class generated from the above source. Because this file is auto-generated, it is encoded using the UTF-8 code page by default.
PicLen.cbl is in the same project. This files stores the source code for a simple COBOL program for assessing the content length of c PIC X(1024) field which is space filled.

If PicLen.cbl is previously existing code or is a new hand-entered source file, it is not encoded using the platform default code page. For example, in the United Kingdom this is code page 1252, or on a Japanese locale machine, it is most likely the Shift-JIS code page 932.

When PicLen is called from WindowStuff, as follows, one code page calls another:

       call "PicLen" using stuff lStuff

Calling one code page from another is not supported directly. When the application runs, it might fail under some conditions, due to corrupt PICTURE clause data items.