1) depends on what your webapps size is. The performance advantage will be seen only in large porojects where objects can be shared between pages/ applications etc. Then I do not have to create the CS file for every web app.

2) see prev point

3) you should be able to . I think u can set your destination dll as a single filename while giving multiple cs files. I do not know the syntax but a quick search at the msdn site will throw some light

compiling all .cs files in a directory called "myDir" (and below)

csc /target:library /out:mylib.dll /recurse: myDir\*.cs

you can pass additional parameters to the compiler, e.g. /debug to get more debugging information, when accessing asp.net pages.

for a full list see
http://msdn.microsoft.com/library/en-us/cscomp/html/vcrefcsharpcompileroptionsbycategory.asp

Hi, does your advice apply to my situation?

I am building an intranet portal using ASP.NET and C#. The portal is conceptually inspired by DotNetNuke & IBS Portal but all of my code is my own. This portal will serve as an entry point for several different reports and applications all in ASP.NET which MUST share the same ASP.NET Forms Authentication model.

So, I have the guts of my portal (i.e the homepage, menu system and nifty little modules for the homepage) compiled into the main dll in the root bin for my portal solution. The additional applications will be initially loaded as modules using a construct similar to the way DesktopDefault.aspx injects modules into the page. Anyway, it is imperative that each application's/module's dll be seperate from the main portal so that each application can be updated, compiled and deployed without affecting a) the portal itself and b) other applications.

Currently each application is its own ASP.NET solution, so each app has its own dll. How do I integrate these apps into my portal's folder structure while keeping their dlls seperate from my main portal dll?

Thank you very much for any assistance you can provide. This one kind of crept up on me all of a sudden ;-)

I figured it out. Compile dlls in their own project. Make sure the same root namespace is used. Copy to root bin folder, copy over aspx/ascx files, viola!

I figured it out. Compile dlls in their own project. Make sure the same root namespace is used. Copy to root bin folder, copy over aspx/ascx files, done.

OK, How can I do this without compiling the dll. My asp won't allow compiled dll's. How do I reference this module (.vb) within the class by href. Any idea'???