Compiling *code behind* into multiple DLLs ?

[Patrice]

Hi all,

I'm currently upgrading a 1.1 application. We were using a command file to
invoke the command line compiler to that we have the code behind compiled
into multiple DLLs (to be able to deploy one "part" of the site while
working on another, this is an intranet that contains related but somewhat
independant "modules").

I first thought it was possible in 2.0 but it seems now that actually this
is only true for ASPX files and that code behind files are still compiled
into a single assembly...

Is this something available out of the box (possibly using the web
deployment addin ?) or do I still need to customize the build process if I
want to compile the code behind into multiple DLLs ?

For now the best option I see would be to hand edit an msbuild file...

Thanks in advance for any advice.

(sorry if doubled post but I don't see my first attempt)

[Michael Nemtsev [MVP]]

Hello Patrice" http:www.chez.com/scribe/,

What type of project are you using?! For the "Web Site" project, not "Web
application" VS 2005 provides the new complilation into multiple assemblies
by default. Specific asp.net folders and contorls will be outputed into separate
dlls

---
WBR,
Michael Nemtsev [Microsoft MVP] :: blog: http://spaces.live.com/laflour

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo
PHi all,
P>
PI'm currently upgrading a 1.1 application. We were using a command
Pfile to invoke the command line compiler to that we have the code
Pbehind compiled into multiple DLLs (to be able to deploy one "part"
Pof the site while working on another, this is an intranet that
Pcontains related but somewhat independant "modules").
P>
PI first thought it was possible in 2.0 but it seems now that actually
Pthis is only true for ASPX files and that code behind files are still
Pcompiled into a single assembly...
P>
PIs this something available out of the box (possibly using the web
Pdeployment addin ?) or do I still need to customize the build process
Pif I want to compile the code behind into multiple DLLs ?
P>
PFor now the best option I see would be to hand edit an msbuild
Pfile...
P>
PThanks in advance for any advice.
P>
P(sorry if doubled post but I don't see my first attempt)
P>

[Patrice]

I'm using the "web application" model (VS 2008) as this is a 1.1 upgrade
plus I used the "Web site" project model for another project and for now it
looks like the "web application" model works better for me...

Is this compilation behavior really tied to the project model used ? Is this
possible to use the "web application" model for development and to invoke
the same commands than for a "web project" model when creating the release
build ?

Else I'll just keep my batch files for 2.0...

Thanks.

--
Patrice

"Michael Nemtsev [MVP]" <ne*****@msn.co ma ecrit dans le message de groupe
de discussion : 90************* *************@m snews.microsoft .com...

Hello Patrice" http:www.chez.com/scribe/,

What type of project are you using?! For the "Web Site" project, not "Web
application" VS 2005 provides the new complilation into multiple
assemblies by default. Specific asp.net folders and contorls will be
outputed into separate dlls

---
WBR, Michael Nemtsev [Microsoft MVP] :: blog:
http://spaces.live.com/laflour
"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

[Patrice]

Finally I just used my previous batch file all along with aspnet_compiler
and aspnet_merge and it seems to produce the desired output...

I thought 2.0 was able to that including fro WAP but I likely missed it was
just for compiled ASPX pages, not for code behind files...

--
Patrice

"Patrice" <http://www.chez.com/scribe/a écrit dans le message de groupe de
discussion : 2B************* *************** **...icrosof t.com...

I'm using the "web application" model (VS 2008) as this is a 1.1 upgrade
plus I used the "Web site" project model for another project and for now
it looks like the "web application" model works better for me...

Is this compilation behavior really tied to the project model used ? Is
this possible to use the "web application" model for development and to
invoke the same commands than for a "web project" model when creating the
release build ?

Else I'll just keep my batch files for 2.0...

Thanks.

--
Patrice

"Michael Nemtsev [MVP]" <ne*****@msn.co ma ecrit dans le message de
groupe de discussion :
90************* *************@m snews.microsoft .com...

>Hello Patrice" http:www.chez.com/scribe/,

What type of project are you using?! For the "Web Site" project, not "Web
application" VS 2005 provides the new complilation into multiple
assemblies by default. Specific asp.net folders and contorls will be
outputed into separate dlls

---
WBR, Michael Nemtsev [Microsoft MVP] :: blog:
http://spaces.live.com/laflour
"The greatest danger for most of us is not that our aim is too high and
we miss it, but that it is too low and we reach it" (c) Michelangelo