ILMerge to protect dll


Author
Message
JSW W.
JSW W.
Supreme Being (127 reputation)Supreme Being (127 reputation)Supreme Being (127 reputation)Supreme Being (127 reputation)Supreme Being (127 reputation)Supreme Being (127 reputation)Supreme Being (127 reputation)Supreme Being (127 reputation)Supreme Being (127 reputation)
Group: Forum Members
Posts: 127, Visits: 1
Are there some solution to protect your dll by some merge operation?
Would there be potential problem?
Reply
Nevron Support
Nevron Support
Supreme Being (4.5K reputation)Supreme Being (4.5K reputation)Supreme Being (4.5K reputation)Supreme Being (4.5K reputation)Supreme Being (4.5K reputation)Supreme Being (4.5K reputation)Supreme Being (4.5K reputation)Supreme Being (4.5K reputation)Supreme Being (4.5K reputation)
Group: Administrators
Posts: 3.1K, Visits: 4.2K
Hello JSW W.,

I've tried to create a new assembly which contains Nevron.Presentation.dll, Nevron.System.dll and Nevron.UI.WinForm.Skins.dll assemblies using ILMerge.
Then I referenced this new assembly and I was able to compile and ran my test project successfully.

To be able to apply skin you should change the value of NSkinResource.AssemblyName property to the name of the assembly that contain Nevron.UI.WinForm.Skins assembly.
Also, if you using Visual Studio 2010 you should change the value of Target Framework property in your project properties to .NET Framework 4.

I hope it helps.

Best Regards,
Nevron Support Team


GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...





Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search