This work around for licensing in not acceptable for my application. I compile TChart into another .Net control. Users of that control have no access whatsoever to any design time functionality of TChart, and I expect that they will be able to use my design time functionality in their projects without a TChart development license.
More directly, my control is used in web pages using the object tag syntax classid="<AssemblyName>#<FullyQualifiedClassName". Your license policy would require that I supply my users with a copy of Internet Explorer compiled under a Steema developer license. This is clearly not going to happen.
When can we expect Steema to correct this error? As an alternative, apparently Version 1 did not have this problem. Can I trade in my unusable version 2 for version 1?
More on license error: object not set
Hello,
It's an interesting use issue. TeeChart License control is pure Microsoft .NET, no special ingredients have been added in. It should work across the board, we'll check into this.
Although an alternative is (and was in earlier v1) not to apply any license control, that has opened the door to misinterpretation of licensed use in the past in some installations where TeeChart has been distributed to support an application and the final installation machine includes a .NET designtime environment.
The behaviour described by you appears to be a feature/limitation of Microsoft Licensing policy however there is documentation available relating to use of .NET licensed controls in Internet Explorer, passing license by params. We'll check to see what solutions are suggested and if TeeChart is missing any ingredient to comply.
Re. Can I trade in my unusable version 2 for version 1?
Yes though we would hope to find a solution that allows a step forward rather than go back a version.
We'll get back to this thread with some more information forthwith.
Regards,
Marc Meumann
It's an interesting use issue. TeeChart License control is pure Microsoft .NET, no special ingredients have been added in. It should work across the board, we'll check into this.
Although an alternative is (and was in earlier v1) not to apply any license control, that has opened the door to misinterpretation of licensed use in the past in some installations where TeeChart has been distributed to support an application and the final installation machine includes a .NET designtime environment.
The behaviour described by you appears to be a feature/limitation of Microsoft Licensing policy however there is documentation available relating to use of .NET licensed controls in Internet Explorer, passing license by params. We'll check to see what solutions are suggested and if TeeChart is missing any ingredient to comply.
Re. Can I trade in my unusable version 2 for version 1?
Yes though we would hope to find a solution that allows a step forward rather than go back a version.
We'll get back to this thread with some more information forthwith.
Regards,
Marc Meumann
Steema Support
Hello,
This issue is being worked through - to create a working demo of a similar setup to the one described. .NET Permissions are hampering progress on a simple test Control before we even get to the issue inhand, so in the meantime I'll post up a reference here that might help you get there more quickly than waiting on us.
http://windowsforms.net/articles/Licensing.aspx
There's a section that deals with Controls in IE.
When we get a more concrete result we'll post it up here.
Regards,
Marc Meumann
This issue is being worked through - to create a working demo of a similar setup to the one described. .NET Permissions are hampering progress on a simple test Control before we even get to the issue inhand, so in the meantime I'll post up a reference here that might help you get there more quickly than waiting on us.
http://windowsforms.net/articles/Licensing.aspx
There's a section that deals with Controls in IE.
When we get a more concrete result we'll post it up here.
Regards,
Marc Meumann
Steema Support
I have to admit that that license technique does work. I can't find any official Microsoft documentation about it, so I have to consider it an undocumented feature that can be removed at any time.
Still doesn't solve the base problem that I compiled your control into my control with a valid run time license, but my control users also have to have your design time license.
Still doesn't solve the base problem that I compiled your control into my control with a valid run time license, but my control users also have to have your design time license.
Hello,
Update
--------
We concur. Information for this is not forthcoming from Microsoft information sources. The fact that the technique described exists means that someone has recognised the need for it. We haven't successfully managed to license a referenced dll via the technique but are continuing investigations and seeking further information.
Regards,
Marc Meumann
Update
--------
We concur. Information for this is not forthcoming from Microsoft information sources. The fact that the technique described exists means that someone has recognised the need for it. We haven't successfully managed to license a referenced dll via the technique but are continuing investigations and seeking further information.
Regards,
Marc Meumann