RE: Winforms: calling 2nd form
Here is what I found:1. this forum article itself in the forum2. A wiki titled "Handle multiple WinForm forms in Visual COBOL"3. A forum article "using 'Call' in Method4. A wiki article "Visual COBOL...
View ArticleWinforms: calling 2nd form
I am working through "Tutorial: Developing .NET Managed COBOL", trying to learn Visual COBOL. I developed Form1, then Menu1 and made it my startup program - all fine and working. Then to extend the...
View ArticleClik here to view.
Visual CoboL .NET Book
Hi guys,Already available in the online bookstore AgBook here, my Visual Cobol .NET book with print option in black and white, in colors or PDF. With more than 50 examples projects distributed in...
View ArticleRE: Visual CoboL .NET Book
Hi Mike, I intend to publish an English version in the middle of next year.
View ArticleRE: Load a DLL
I will try to explain what happens. Here in Brazil we have to do tax changes and the government unified the sending of information and he is using this dll, I made another program NetExpress and the...
View ArticleRE: Load a DLL
The same call code that you used under Net Express should work in a managed COBOL program as well including the call-convention, etc.To make the native code .dll available for the call you can either...
View ArticleRE: Load a DLL
Using the same format NetExpress of the following error: {"% d error message text not found \ n (Could not load file or assembly 'file: /// c: \\ \\ sat SAT.dll.' or one of its dependencies The module...
View ArticleLoad a DLL
Good morning, I'm needing to load a dll and I find nothing in Cobol for this, but I found the instructions in VB <DllImport("c:SATSAT.dll", CallingConvention := CallingConvention.Cdecl)> _Public...
View ArticleRE: Load a DLL
The error that you are seeing is caused by calling a native .dll that is a different bitism than the calling managed program.If this is a 32-bit .dll that you are calling then the managed code project...
View ArticleRE: FirstChanceException logging
The following example works for me. This will attach a method to the firstchangeexception event and then will raise an exception to see it execute. The handler will write the exception to the event...
View ArticleRE: FirstChanceException logging
Thanks. My application is multi-threaded and I got the mutex statement working. I couldn't find a reference to the sync statement. C# has a SyncLock statement. Would that be it?
View ArticleRE: FirstChanceException logging
You can find SYNC documented under the General Reference-->Managed COBOL-->Statements section hereYou can place SYNC on the method or you can surround a block of code like:Within an object:SYNC...
View ArticleRE: COBOL instrumentation in Visual Studio
Instrumentation is built in to Visual Studio, and appears to work on parts of COBOL code, but not all. Is the Micro-Focus answer to this that we have to purchase DevPartner to get full Instrumentation...
View ArticleCOBOL instrumentation in Visual Studio
I am tasked with trying to find ways to improve performance of Visual COBOL application. The Visual Studio Instrumentation appears to match to symbols from COBOL code for some functions, but in many...
View ArticleRE: Splash Screen
For what type of application, Windows Forms, WPF, ASP.NET?What did you want to display on the splash screen, bitmap, progress bar, etc.?
View ArticleRE: Product license error
Please review this POST as it may provide an answer, if it does not, please email your product mainteannce Serial Number and the details of this post to SupportLine@MicroFocus.com.
View ArticleRE: Product license error
If you created these .dlls using Visual COBOL for Visual Studio 2013 then you need to run these using the COBOL Server 2013 product and not the COBOL Server 2012 product. If you want to install your...
View ArticleRE: Product license error
HI Chris,Sorry for the confusion, we are using cobol server 2013.As mentioned in step 3, do we need to copy all the files in bin folder and other exe's from the server installed with cobol server 2013...
View ArticleProduct license error
We have converted NX based dialog system to Visual cobol dialogs and generated the application dll’s using Visual studio 2013 and it works good as expected in my development environment.I have deployed...
View Article