[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 204
  • Last Modified:

DLLs & ASP.Net

What are the pros and cons of compiling code to a DLL to be used in an ASP.Net application?
Ray Turner
Ray Turner
1 Solution
I can only think of 3 pros and 1 con. I'm sure I could google more but heck so could you so Im thinking you're looking for what's in people's heads...

1. Pre-compiling makes the server run faster initially.


Even if you don't pre-compile your .aspx pages into .dll's the server will compile them for you the 1st time someone tries to open a page. They then remain compiled (virtually) for the length the server session stays alive.

It amounts to the same way it takes longer the 1st time you debug a solution in VS vs just refreshing the same debug session. Next time you put up a site, or even change a page, go to the site and note on the 1st load everything takes a little longer... it's compiling.

2. If you pre-compile you will never crash your site due to some faulty code that wont compile. This is a small matter and certainly there are various other ways you might crash your site with code that is already compiled :)

3. Security! No one will be able to see or change your code except those you give access to the original code base (well not technically anyway). You can even put up code for people who haven't paid you yet with the reasonable assertion that they wont steal your work and go out of business so easily, etc.


1. Its a little more work to keep track and maintain things. I wouldn't even say "more" so much as "different".

That's my .02
Ray TurnerSenior ConsultantAuthor Commented:
Thanks for your .02!

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now