Thursday, March 19, 2009
NiXPS assembly can now be referenced in .NET
A lot of our customers are using the NiXPS SDK in a .NET environment.
As our SDK is essentially a 'native' (unmanaged) library, it can be used in .NET via managed/unmanaged interop.
We have shielded this complexity for the user, and provide a C# object model that in its implementation calls further into the native NiXPS dll.
Now, for v2.6.2 we went a step further and are releasing a fully integrated .NET assembly.
This assembly is a class library that contains the object model, and has also the native NiXPS dll embedded.
As a result a .NET developer doesn't need the C# glue objects anymore, he now only needs to reference the NiXPS assembly to be able to work with our SDK.
(This will be part of the upcoming v2.6.2 release; the integrated .NET assemblies can be found in the bin/.net folder in the SDK archive.) ¶ 15:35
A lot of our customers are using the NiXPS SDK in a .NET environment.
As our SDK is essentially a 'native' (unmanaged) library, it can be used in .NET via managed/unmanaged interop.
We have shielded this complexity for the user, and provide a C# object model that in its implementation calls further into the native NiXPS dll.
Now, for v2.6.2 we went a step further and are releasing a fully integrated .NET assembly.
This assembly is a class library that contains the object model, and has also the native NiXPS dll embedded.
As a result a .NET developer doesn't need the C# glue objects anymore, he now only needs to reference the NiXPS assembly to be able to work with our SDK.
(This will be part of the upcoming v2.6.2 release; the integrated .NET assemblies can be found in the bin/.net folder in the SDK archive.) ¶ 15:35
