Quantcast
Channel: Visual COBOL
Viewing all articles
Browse latest Browse all 5819

Forum Post: RE: VC 2.1 to 2.3

$
0
0
Hi Chris Thank you for the reply. So, on the Windows 10 pc I set the Target Framework for every project in the App to .NET Framework 4.5.2.  I now have a problem I need help with: One project in the App is a Windows Forms project, called from another Windows Form.  This project also contains a class (called Amends) that contains public methods to read to extract information from data files and pass back to the main form.  This class is instantiated from the Form_Load handler of the form.  The constructor in this class opens the data file.  The App is crashing on the line            set cls-amend to new Amends. where cls-amends is of type Amends.  The class definition for Amends with constructor is:         class-id Amends.        ENVIRONMENT DIVISION.                                             ...        DATA DIVISION.                                                   ...        method-id NEW.        procedure division.        IN010.    *        Open data file.            goback.        end method. * public methods ...        end class. When I change the Output Type for this project to Windows Application and run in VS the last three lines of the Output window are: Exception thrown: 'System.InvalidProgramException' in IPAMENDS.exe 'IPAMENDS.exe' (Managed (v4.0.30319)): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\Microsoft.VisualStudio.Debugger.Runtime\14.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Debugger.Runtime.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled. The program '[8028] IPAMENDS.exe: Managed (v4.0.30319)' has exited with code -1073741819 (0xc0000005) 'Access violation'. The same thing happens when I change the Target Framework back to .NET Framework 4 Client Profile or .NET Framework 4.6.1, or when the project is called from the main App form as a dll.  No code changes have been made from VC 2.1 to VC 2.3, the only thing changed is Target Framework.  I am also puzzled as to why (Managed (v4.0.30319)) appears in the Output Window when the Target Framework is 4.5.2. I searched for this error and Microsoft says it may be a bug in the compiler. Other details: Windows 10 Pro version 10.0.10586 Build 10586 Microsoft Visual Studio Community 2015 version 14.0.25431.01 Update 3 Micro Focus Visual COBOL 2.3 Version 2.3.00134.  Trial version. Microsoft .NET Framework version 4.6.01038 Platform Target for all projects in App is Any CPU. Thank you Brendan

Viewing all articles
Browse latest Browse all 5819

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>