Dave Burke : Freelance .NET Web Developer specializing in Online Communities

ASP.NET Ajax and Community Server: Trim your Toolkit

This is a basic ASP.NET rule that's easy to forget, but if using the ASP.NET Ajax Control Toolkit with another application like Community Server, we score big if we remember to trim the toolkit of the code we don't need.

 


The full Ajax Control Toolkit project DLL like the above weighs in at 1332KB when compiled in Debug mode and 764KB in Release mode.  We've customized the Toolkit's SlideShow control for Community Server and added a Web Service in the Toolkit project in a /Services folder.  So we can exclude (not remove so we can quickly include them later) all of the controls we're not using.  The resulting Ajax Toolkit DLL in our Community Server /bin directory is only 220KB.


Comments (2) | Post RSS RSS comment feed

Posted on 5/28/2007 10:34:42 PM by Dave Burke
Categories: .NET | Community Server
Tags: no tags for this post

Related posts

Comments (2) -

5/29/2007 12:25:32 AM Permalink

Dave,

You gotta remember though, loading each assembly has a bunch of overhead too. is 600K really going to affect the performance of the site when there are 32 assemblies already in the BIN folder? You'd probably get a higher performace increase if Telligent moved all the MailGateway stuff from 3 separate assemblies into one assembly, just for starters.

And, Microsoft says that performance actually improves if you Strong Name Sign assemblies, because the runtime doesn't have to do any of the hash checking it does with non-signed assemblies. So if Telligent installed the assemblies to the GAC, performance would improve there as well.

Robert W. McLaws |

5/29/2007 8:18:32 AM Permalink

Excellent points, Robert.  Thanks a lot.  I didn't know about the performance boost with signed assemblies.

daveburke |


Powered by BlogEngine.NET 2.0.0.36
Theme by Dave Burke