G
Guest
Hello. I have this situation, and I don't know where to find an answer for
the issue; it's pretty advanced, but I hope somebody else already went
through this pain, and found the correct solution and help me out, as I'm
spending hours and hours on it without any result but frustration:
In a very simple ASP .NET page, Default.aspx, we will host a WinForms
control, let's call it WrapperControl. The WinForms control is defined in a
custom Windows control library assembly, let's call it WrapperAssembly.
The WrapperControl inherits from a BaseControl class, defined in a
referenced assembly, named BaseAssembly (in the WrapperAssembly there is a
reference to BaseAssembly).
The BaseControl (from BaseAssembly) is the one which needs licensing. I have
the .LIC file for BaseAssembly, installed in the folder that contains the
referenced DLL.
In WrapperAssembly.dll we embed the license for BaseAssembly as we have a
correct License.licx file (and can do it even by hand, using LC.exe,
generating .licenses file, which can later be added to WrapperAssembly.dll at
building time using /resource parameter for compiler).
If WrapperAssembly.dll would be WrapperAssembly.exe, and we would run it,
loading he control on screen, it would run correctly, without any issues, of
course.
But as we host WrapperControl from WrapperAssembly.dll on Internet Explorer,
this means that the "most outer" assembly would be... none (or Internet
Explorer.exe). And that would be the assembly which we should embed our
license file on.
I found this article - http://windowsclient.net/articles//licensing.aspx -
and a few others (similar) describing how to use the LC.exe-compiled
..licenses file in a web page, using the LINK REL="licenses" approach (in
HEAD).
I tried that in multiple ways already but however, no matter what, there is
no way I can get the BaseControl stop complaining that it's not licensed when
WrapperControl is loaded in the IE page.
If someone knows what could be wrong here - I'd appreciate if he or she
could help. Thanks in advance.
the issue; it's pretty advanced, but I hope somebody else already went
through this pain, and found the correct solution and help me out, as I'm
spending hours and hours on it without any result but frustration:
In a very simple ASP .NET page, Default.aspx, we will host a WinForms
control, let's call it WrapperControl. The WinForms control is defined in a
custom Windows control library assembly, let's call it WrapperAssembly.
The WrapperControl inherits from a BaseControl class, defined in a
referenced assembly, named BaseAssembly (in the WrapperAssembly there is a
reference to BaseAssembly).
The BaseControl (from BaseAssembly) is the one which needs licensing. I have
the .LIC file for BaseAssembly, installed in the folder that contains the
referenced DLL.
In WrapperAssembly.dll we embed the license for BaseAssembly as we have a
correct License.licx file (and can do it even by hand, using LC.exe,
generating .licenses file, which can later be added to WrapperAssembly.dll at
building time using /resource parameter for compiler).
If WrapperAssembly.dll would be WrapperAssembly.exe, and we would run it,
loading he control on screen, it would run correctly, without any issues, of
course.
But as we host WrapperControl from WrapperAssembly.dll on Internet Explorer,
this means that the "most outer" assembly would be... none (or Internet
Explorer.exe). And that would be the assembly which we should embed our
license file on.
I found this article - http://windowsclient.net/articles//licensing.aspx -
and a few others (similar) describing how to use the LC.exe-compiled
..licenses file in a web page, using the LINK REL="licenses" approach (in
HEAD).
I tried that in multiple ways already but however, no matter what, there is
no way I can get the BaseControl stop complaining that it's not licensed when
WrapperControl is loaded in the IE page.
If someone knows what could be wrong here - I'd appreciate if he or she
could help. Thanks in advance.