L
Lucia
I'm working at .NET project to implement a COM
interface for a .NET control.
The .NET assembly is built with the correct license for the control.
Some unmanaged code is creating an instance of the control,
inside an MFC dialog.
When the control is used inside a WinForm dialog, the license
is correctly validated and everything works.
However, when the control is used inside the MFC dialog,
the license doesn't seem to be loaded/validated.
In fact, I get a dialog showing that the control I'm using is an
evaluation version (that is not, btw)
Is this a problem caused by the interaction of managed and unmanaged
code?
If yes, anyone knows a way to force the license to be loaded from
unmanaged code?
Any suggestion is appreciated.
Thanks,
Lucia
interface for a .NET control.
The .NET assembly is built with the correct license for the control.
Some unmanaged code is creating an instance of the control,
inside an MFC dialog.
When the control is used inside a WinForm dialog, the license
is correctly validated and everything works.
However, when the control is used inside the MFC dialog,
the license doesn't seem to be loaded/validated.
In fact, I get a dialog showing that the control I'm using is an
evaluation version (that is not, btw)
Is this a problem caused by the interaction of managed and unmanaged
code?
If yes, anyone knows a way to force the license to be loaded from
unmanaged code?
Any suggestion is appreciated.
Thanks,
Lucia