Multiple DLLs for a single Website ?

  • Thread starter Thread starter Patrice Scribe
  • Start date Start date
P

Patrice Scribe

Any guidance available for this. I know it will be easier in Whidbey but for
now we'll have a single site made up of distinct modules.

What are the options ? :
- single DLLs (not that conveniant when mutiple modules are under revision)
- mutliple DLLs AFAIK not supported by VS.NET but likely possible using the
command line compiler ?
- managing each subsite as a distinct project (but ability to share the same
session ?)

Any advice ? TIA.

Patrice

--
 
It looks like :
- having a project for each "subpart" but its DLL still going to the main
/bin directory
- the root for each "subpart" is not defined as an application root
would work.

Also it is likely it could be done also with a single project and compiling
using the compiler from a batch file using the same layout than above would
work (didn't had time yet to try this)

Once the DLLs are on my build server it would allow to update only the
needed part by copying only the right "subpart" and its associated DLL.

Anyone came across something describing a similar layout ?

Patrice
 
Looks like the easiest way is to use the command line compiler ot create a
DLL for each subweb. It allows also to switch easily between both models...

Patrice

--

Patrice Scribe said:
It looks like :
- having a project for each "subpart" but its DLL still going to the main
/bin directory
- the root for each "subpart" is not defined as an application root
would work.

Also it is likely it could be done also with a single project and compiling
using the compiler from a batch file using the same layout than above would
work (didn't had time yet to try this)

Once the DLLs are on my build server it would allow to update only the
needed part by copying only the right "subpart" and its associated DLL.

Anyone came across something describing a similar layout ?

Patrice

--
Click to expand...
 
Back
Top