D
D
dnv7772012-02-21 20:52:13
IIS
dnv777, 2012-02-21 20:52:13

IIS7. Asp.Net : Is it possible to make different sites look at the same assembly?

There are over a hundred sites in IIS, with a common engine, ie. all refer to the same folder. Each site has its own _res virtual folder, no web.config and .net files, only css templates, documents, etc.
When there were few sites, everything was fine, but now, with every update of the files in the App_Code folder, all sites seriously slow down, because. each copy of the site is compiled separately. This can be seen from HttpRuntime.CodegenDir

The assembly is projectless, the site is under rapid development, sometimes you need to urgently fix a glitch in some page or a common class, and lay it out. The time to recompile and load the entire site can be critical. Therefore, at this stage of site development, I cannot use precompilation.

There is an option to simply add different urls to one site in IIS, but then you will have to abandon the global variables (I store them in a static class), of which there are a lot, or convert each variable to a Property, and then get / set the value by key (url). But a lot will have to be redone, on many pages these variables go in a cycle, which means they need to be cached so that performance does not drop.

Is it possible to specify in IIS7 that all sites look at one assembly, and, accordingly, so that with any change, compilation takes place only once?

Answer the question

In order to leave comments, you need to log in

2 answer(s)
D
Denisio, 2012-02-21
@Denisio

to install in the GAC?

C
catlion, 2012-02-22
@catlion

> Each site has its own _res virtual folder, without web.config and .net files, only css templates, documents, etc.
Or maybe it’s better to hang all domains on one application, map each domain to a folder inside it, and resolve requests using HTTP/ISAPI modules?

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question