C
Curt_C [MVP]
Are you asking how to split em? Simply create them as multiple applications
all under one project. That should work.
all under one project. That should work.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
W
WJ
applications all under one project. That should work.Curt_C said:Are you asking how to split em? Simply create them as multiple
Should it be multiple projects under one "solution" ? Because if under one
project, everything is packed into one assembly (dll).
John
C
Craig Deelsnyder
Yes, each project gets compiled into an assembly (and can also containapplications all under one project. That should work.
Should it be multiple projects under one "solution" ? Because if under
one
project, everything is packed into one assembly (dll).
John
other assemblies it references). So you'd create different projects for
each 'module' you'd like to share, probably as Class Library projects.
Then reference those projects or their resulting dlls in the projects that
will need to use them.
C
Curt_C [MVP]
OP indicated they wanted a seperate DLL for each I thought....
Curt
Curt
J
Jens Christian Mikkelsen
raffe said:I'd like to be able to have one dll for every module in my web applicarion.
At the same time I'd like those modules to share all the session variables,
configuration, application domain, etc. Anybody has done that before?
I believe this is described in knowledgebase article 307467:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;307467
Some of my colleagues at work have tried this for a large conversion
project, so it can be done. Don't know if there are any issues with it,
though.
Jens
R
raffe
I'm working on an Web Application. Visual Studio has a great support for
that. But as my application grows in functionality I'd like to split it into
modules. I can't see any othrer possibility than having one web - one web
assembly (dll).
I'd like to be able to have one dll for every module in my web applicarion.
At the same time I'd like those modules to share all the session variables,
configuration, application domain, etc. Anybody has done that before?
Rafael
that. But as my application grows in functionality I'd like to split it into
modules. I can't see any othrer possibility than having one web - one web
assembly (dll).
I'd like to be able to have one dll for every module in my web applicarion.
At the same time I'd like those modules to share all the session variables,
configuration, application domain, etc. Anybody has done that before?
Rafael