Search found 8 matches
- Fri Jun 01, 2007 1:56 pm
- Forum: .NET
- Topic: Licensing changed after upgrade from VS2003 to VS2005
- Replies: 18
- Views: 24233
Marc, Thank you for continuing interest in this issue. I would be interested in trying out the new assembly, please me know what changes you made to the licensing mechanism and how I can get the new package. I did receive your earlier email at my work address but was too busy to respond until now. Y...
- Wed May 23, 2007 8:16 pm
- Forum: .NET
- Topic: Licensing changed after upgrade from VS2003 to VS2005
- Replies: 18
- Views: 24233
Marc, Non-restricted version, while technically satisfying our needs, require that we distribute the unprotected TeeChart.dll with our product. This is far from ideal. I am not sure it is even within our right. This is still something that we need to determine. We intend to make our application avai...
- Wed May 23, 2007 6:02 pm
- Forum: .NET
- Topic: Licensing changed after upgrade from VS2003 to VS2005
- Replies: 18
- Views: 24233
Marc, I think I understand your position. You want to ensure that any binary that loads TeeChart directly or indirectly at run time was compiled with a design time license to the TeeChart. So for example, if you had: exe -> assembly 1 -> assembly 2 -> TeeChart assembly, then you want to place a lice...
- Wed May 23, 2007 4:01 pm
- Forum: .NET
- Topic: Licensing changed after upgrade from VS2003 to VS2005
- Replies: 18
- Views: 24233
Marc, Assembly.LoadFrom or similar alternatives are the key - it allows the plugin architecture to work. Keep in mind the outlook.exe example, a 3rd party vendor needs to be able to deliver a plugin assembly not known to Microsoft at build time. So outlook.exe will do exactly what I am doing - call ...
- Tue May 22, 2007 4:17 pm
- Forum: .NET
- Topic: Licensing changed after upgrade from VS2003 to VS2005
- Replies: 18
- Views: 24233
Marc, Sorry for double post but I forgot to mention something. If I add licenses.licx file to the HostApp project and try to build it on the same box (with design license present). it fails to build with the following output: C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\bin\LC.exe /target:Hos...
- Tue May 22, 2007 4:04 pm
- Forum: .NET
- Topic: Licensing changed after upgrade from VS2003 to VS2005
- Replies: 18
- Views: 24233
Marc, I made a simple project to illustrate the problem. Basically I have a solution with 4 projects in it: HostApp (exe) PluginShared (dll) assembly which defines a factory interface Plugin (dll) a simple plugin which does not use chart PluginWithChart (dll) another simple plugin which does use cha...
- Tue May 22, 2007 12:33 pm
- Forum: .NET
- Topic: Licensing changed after upgrade from VS2003 to VS2005
- Replies: 18
- Views: 24233
Marc, As I have mentioned, TeeChart control is installed on the build host. Both main application and plugin are built on that host. And, in fact, I did ran registration utility as you are suggestion (just in case) I can compile add-in with TeeChart reference on the build server. When I attempt to l...
- Mon May 21, 2007 8:44 pm
- Forum: .NET
- Topic: Licensing changed after upgrade from VS2003 to VS2005
- Replies: 18
- Views: 24233
Licensing changed after upgrade from VS2003 to VS2005
Hello, We have a .NET 1.1 WinForms application which does not itself use the TeeChart control. The application manually loads an add-in assembly which uses the TeeChart for .NET v2 control. At some point in the past, it was explained to us that even though the main application itself did not use or ...