Posted by codinglifestyle in SharePoint.
Tags: assemblies, GAC, SharePoint, static linking
I came upon an exciting article on codeproject which allows static linking ASP.NET assemblies. One of the issues I commonly run up against when developing WebParts is avoiding linking to excess dlls due to the additional work involved in modifying the security policies. You can always throw each assembly in the GAC if you developed them yourself however to me it seems sloppy to register 5 assemblies in the GAC for a single web part. The project makes it a simple post-build step to de-compile .NET assemblies and then build them all into one primary assembly. This means just one assembly to throw in the GAC or add to your policy. For me this will greatly reduce cut and pasting in the future.
Here is the project: