Following the recent release of Visual Studio 2005 and .NET 2.0, I’d like to disclose some of the things we’ve been working on recently.
Because of the new features in .NET 2.0, it is now possible to use LM-X from a mixed-mode class library. Performing local and network (floating) licensing from your .NET applications is now even easier than before.
I find C++/CLI, especially, to be a very nice new contribution; it really makes it much easier to use C++ in the .NET environment.
Consequently, in the upcoming version of LM-X, we will have even more language support than previously.
Until now, LM-X has worked with C#, VB.NET and Managed C++. Since Managed C++ has been replaced with C++/CLI, this will also be supported from now on. In addition, J# will also be supported.
Personally, though, I have mixed feelings about .NET. Besides the fact that you can use all the features of LM-X in .NET on both Win32 and Win64, there are a few other additional problems. Although you can use all of LM-X’s features under .NET in both Win32 and Win64, we have encountered some issues under .NET and, although it certainly has its numerous good points, I suspect there are also many problems with the latest VS2005 release that are just waiting to be found. In fact, I really think that this release of .NET was put out in too much of a hurry.
These problems will affect both LM-X and many other (3rd party, non-copy protection/licensing-related)applications, too. For example, it seems Microsoft does not have too much faith in J#: they’ve made the decision not to port it to 64 bit. Since we provide mixed mode class libraries, that means we won’t be able to to support J# under Win64.
This is, to my mind, a really big limitation. Still, on the other hand it does seem that support for J# has not been too great, and that there don’t seem to be too many developers interested in using it – as can be seen from the lack of activity on Microsoft’s own beta forum (MSDN Forum – Visual J# General).
Also, the syntax issues in VB can be annoying. An example is (VB ignores “out” parameters ); also, the namespacing bug (Static function bug).
The one that beats them all, though, is the CRT manifest problem, which really is a big issue (Unable to load class library problem).
Unfortunately, these are just the tip of the iceberg when it comes to the problems we have run into lately.
But never fear! I am an optimist. Eventually, I’m sure there will be so many complaints that Microsoft will be forced to deal with them. A lot of time was spent on finding workarounds on these issues but I think it will all pay off in the end.
The ride has been bumpy, and many bugs were found, but the improved .NET interface we provide gives application developers a new and improved way to interface LM-X which will, I am sure, be appreciated once people start adopting .NET 2.0 and to need license management.
