I'm also one of those who would like to use classes on several web pages.

There is the the convenient way to put those clases into the App_Code folder. Was fine at the beginning, but as my web site get larger and larger it is not nice any more as every little change in the class recompile the whole application.

So what possibilites do I have if I would like that when I change something to my class only the really depended files are recompiled?

Before posting I did my best to search here in the forums about what to do - and I found several hints which says that I could put my classes also in a seperate class librarie with their proper dll. The problem is only that I do not have the faintest idea how to do that :-(

Also - does that really solve my problem? How does my the compiler know which 2 files he has to recompile (The class which would like to share is used by two webpages) ?.

Isn't there an simple way a little bit like in c++ with the header files? I tried to use the #using directive to tell the compiler that he should look for my self made class - but I'm not able to make him find the file.

Any help would be fantastic.

Klaus

klaus1111:

and I found several hints which says that I could put my classes also in a seperate class librarie with their proper dll.

 When you put your classes into separate class libraries, those class libraries will be separate projects which when compiled will give you a dll

You would then put this dll into the bin folder of your web app.

Thus you would decouple the recompilation of your class library and the web application. Whenever you recompile your class library, you will just have to replace the existing dll in the bin folder of your web app provided the changes do not break your existing code in the web app. If the changes are major then you will have to reompile the web app.

Even using precompiled DLLs in place of source_code will cause you headaches.  I'm currently in a similar predicament right now.  We tried using precompiled DLLs, and the site still hung on startup because the system makes shadow copies of all the binaries before fully loading.  In our situation we have 30+ megs of compiled DLLs, and 50 sites running off the same source code.  When a change is made, those DLLs get shadow copied 50 times causing some major slow down.

We're looking for a solution to this.  So far I haven't had much luck.  Anyone out there have any ideas for a solution?  I've been toying with the idea of moiving the classes/app_code outside the application into web services, but I don't know for certain if it'll help.

Does anyone know for certain if, when the content in app_code changes, is the entire site recompiled, or just the content associated with the pages which are hit?  This is significant for us because we have a front page which takes most of the hits, and has several webuser controls and classes associated with it.