...
If you get C# (csc.exe) errors, your compiler executable file csc.exe is not recognized as an internal or external command.
...
To resolve this issue, make sure the .NET framework location is included in your PATH variable . For example:
...
(for example, the location for .NET framework is: C:\Windows\Microsoft.NET\Framework\v4.0.30319
...
).
A "bad key" failure
If you do not reuse your existing LM-X security configuration file for the lifetime of your application, you may get "bad key" failures between license generators, license server and licensed applications.
...
To fix this problem, make sure your environment variable is set to the path of version 1.6 or newer of the JDK.
First-time exceptions in Visual Studio
When the debug mode is enabled, the debugger gets the first chance to see all exceptions before the program does. If the debugger allows the program execution to continue, the program will see the exception as usual. If the program does not handle the exception, the debugger gets a second chance to see the exception, normally causing the program to crash if the debugger were not present.
When running an application with a debug mode enabled in Visual Studio, you may see the following message in the output window: "First-chance exception at 0x76c1b727 in yourapp.exe: some_exception_type at memory location 0x0033411c"
The above message doesn't indicate that LM-X didn't handle an exception, but only notifies you that the exception occurred. If LM-X handles the exception gracefully, no second chance exception will appear.
Please note that LM-X guarantees exception safety and doesn't leave any exceptions unhandled, even if they occur internally.