-
At the recent Microsoft Worldwide Partner Conference, Microsoft honored Alchemy Solutions with the 2010 Sales Momentum Award, underlining our achievements in bringing mainframe organizations to the .NET environment.
-
New NeoData Releases from Alchemy Solutions Speed Mainframe Data Migration and Reduce Associated Risk
-
Unify Selects ATERAS and Alchemy Solutions for Migration of State Agency's Mainframe Systems to .NET Framework
-
This tutorial describes how you can develop NetCOBOL for .NET routines, and use the added functionality that .NET has to offer from your NetCOBOL for Windows COBOL code. In order to do this, Your NetCOBOL for Windows code relies on the same feature it did to call an ActiveX DLL (see video of NetCOBOL for Windows calling a VB6 ActiveX DLL for reference). This layer is called the Component Object Model or COM. COM works in conjunction with .NET by the use of two tools...
-
One of the key design goals in NeoKicks is to leave customers with a true ASP.NET application. One of the benefits of this is that you can leverage tools that are available on Windows for ASP.NET applications to help debug problems that you may be experiencing. The challenge, however, is knowing what those tools are and how to use them, so this will be one of a few different blog posts on the subject of debugging and diagnostics that may help you. We focus a lot on NeoKicks applications, but...
-
The NeoBatch Server is hosted in IIS and is placed into its own IIS application pool. For some kinds of online applications, it is helpful that IIS has automatic settings that periodically recycle/restart the application pool in order to start anew. In the case of the NeoBatch Server, however, having the application pool recycle at undefined times is a very bad thing, because any jobs that the server has spawned will be abandoned and not be able to complete.
-
This tutorial describes how you can develop VB.NET routines, and use the added functionality that .NET has to offer from your NetCOBOL for Windows COBOL code. In order to do this, Your NetCOBOL for Windows code relies on the same feature it did to call an ActiveX DLL (see video of NetCOBOL for Windows calling a VB6 ActiveX DLL for reference). This layer is called the Component Object Model or COM. COM works in conjunction with .NET by the use of two tools (TLBExp and RegAsm).
-
This tutorial describes how you can develop NetCOBOL for C#(CSharp) routines, and use the added functionality that .NET has to offer from your NetCOBOL for Windows COBOL code. In order to do this, Your NetCOBOL for Windows code relies on the same feature it did to call an ActiveX DLL (see video of NetCOBOL for Windows calling a VB6 ActiveX DLL for reference). This layer is called the Component Object Model or COM. COM works in conjunction with .NET by the use of two tools (TLBExp and RegAsm).
-
This video covers the basic steps that you need to take a .NET DLL and make it visible to COM(component object mode), so that your NetCOBOL for Windows routines can access them. It covers the Type Lib Exporter(TLBExp), the Register Assembly routine(RegAsm) and touches upon the Global Cache Utility (gacutil). Download the sample source code used in this tutorial.
-
A prior video shows you how you can create a DLL that simply calls a Windows API with no other calls embedded in the same program. This tutorial shows you how you can combine COBOL Program calls with Windows API calls in-line in the same program by use of an "Entry File" while still utilizing your compiler options you need. Download the sample source code used in this tutorial.
