Hi Christoph,
Use of ILMerge is problematic with our assemblies. There are several areas which could cause issues.
- Licensing - some of our controls allow instantiation by other Syncfusion assemblies without licensing checks. This kind of internal use will run into trouble when assemblies are merged.
- Reflection - we use a fair amount of reflection and at least some it will run into trouble. Also, to be considered is the effect that this will have on serialization.
We have tried this approach in the past and never quite got it working.
Is your purpose easier deployment? If so we suggest using a stub that contains packed assemblies. At runtime the stub can extract required assemblies. This approach offers easy deployment and at the same time does not impose potential runtime constraints. Please let us know if you would like additional information on this approach.
Thank you for using Syncfusion products.
Best regards,
Daniel
>Is it possible to use ILMerge in combination with Syncfusion? I want to pack all the needed Syncfusion DLLs in one single assembly.
If it is possible, which of the Syncfusion assemblies is the primary assembly?
