The SitePoint Forums have moved.

You can now find them here.
This forum is now closed to new posts, but you can browse existing content.
You can find out more information about the move and how to open a new account (if necessary) here.
If you get stuck you can get support by emailing forums@sitepoint.com

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Whether or not you compile your code into DLL's depends on three questions...

1. Is your source code a trade secret? Does the code need to remain secret?
2. Would this component be more scalable if it was a DLL? 3. Are performance enhancements dramatic as a DLL over script code?

My main reason is the speed issue, I am designing a fairly large ecommerce app so speed is becoming a big issue and just wasn't sure if everything could be compiled into a dll or if certain elements had to saty in pure .asp or .htm form.

If you have lots of seperate files for the DLL, imho, the speed increase wont be as much because the OS as to `navigate` between files rather than just seek in one file. However, it would be harder to keep one big file up to date. Depending on what you are building the DLL in, some programs give you options of easily updating resources in your projects automatically (i.e. as soon as they are modified).