Hi,
First of all, congratulation for a great product.
I would like to Merge Actipro Syntax Editor + Web Language add-ons in my own dll/exe.
After being unsucessful to do so and some research, it appears clearly that .net component licensing is a real pain and won't permit to do so (at least using the standard approach).
I have read the few posts regarding ILMerge in the forum and they are confusing. In those posts, some people say that they have found a way which is IMO misleading. The solution they have found rely on embedding the dll's and not merging them. That may not make much difference in many cases but it is clearly different. You still have to deal with the originial dll's and may need to take specific actions regarding security context.
I would like to provide some input on the rationale behing merging rather than embedding or having the dlls:
When building a complete winform/wpf application, it will usually not matter to deal with all those 3rd party dlls.
In other situations, when one is building a component that extends some application, and needs to specify CAS (code access security) rules in some config file (this is the case for reporting services for instance), the more component you are using the more tiedous it is to debug/deploy/upgrade your own component.
SSIS (Integration services) will need one's component and its associated dlls all other the place - x86 - x64 - GAC. Once again, the ability to merge proves extremely useful.
It should be possible to provide an alternative license initialization approach through code. Some other components vendor have provided such an alternative. See the following post for instance:
http://www.mindscape.co.nz/forums/Thread.aspx?PostID=4839
As far as I can see, the alternative approach does not defeat the initial purpose of .Net component licensing and still allow ILMerging the assemblies.
Is there any chance that you look into this?
Thanks in advance.
First of all, congratulation for a great product.
I would like to Merge Actipro Syntax Editor + Web Language add-ons in my own dll/exe.
After being unsucessful to do so and some research, it appears clearly that .net component licensing is a real pain and won't permit to do so (at least using the standard approach).
I have read the few posts regarding ILMerge in the forum and they are confusing. In those posts, some people say that they have found a way which is IMO misleading. The solution they have found rely on embedding the dll's and not merging them. That may not make much difference in many cases but it is clearly different. You still have to deal with the originial dll's and may need to take specific actions regarding security context.
I would like to provide some input on the rationale behing merging rather than embedding or having the dlls:
When building a complete winform/wpf application, it will usually not matter to deal with all those 3rd party dlls.
In other situations, when one is building a component that extends some application, and needs to specify CAS (code access security) rules in some config file (this is the case for reporting services for instance), the more component you are using the more tiedous it is to debug/deploy/upgrade your own component.
SSIS (Integration services) will need one's component and its associated dlls all other the place - x86 - x64 - GAC. Once again, the ability to merge proves extremely useful.
It should be possible to provide an alternative license initialization approach through code. Some other components vendor have provided such an alternative. See the following post for instance:
http://www.mindscape.co.nz/forums/Thread.aspx?PostID=4839
As far as I can see, the alternative approach does not defeat the initial purpose of .Net component licensing and still allow ILMerging the assemblies.
Is there any chance that you look into this?
Thanks in advance.
