web.config and global.asax

[Mark]

I have two projects - they both need to use the same web.config file, the
same global.asax file, and share a common "look and feel" via several user
controls.

Is there an easy way for two projects to share these resources in VS.NET so
we don't have to worry about synchronization issues ASIDE from combining the
two projects into one?

Thanks in advance!
Mark

[Cowboy \(Gregory A. Beamer\)]

Not directly. You can fudge the global.asax by encapsulating the
functionality into a class library and calling the routines from each
global.asax. For the config, you are largely on your own, as configs work
for one project; the only solution I can think of is to create a separate
config type file.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

************************************************** ********************
Think Outside the Box!
************************************************** ********************
"Mark" <fi**************@umn.edu> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl...

I have two projects - they both need to use the same web.config file, the
same global.asax file, and share a common "look and feel" via several user
controls.

Is there an easy way for two projects to share these resources in VS.NET so we don't have to worry about synchronization issues ASIDE from combining the two projects into one?

Thanks in advance!
Mark

[Mark]

Thanks Greg.

What would be impact of putting these two projects (.dll) in the same
virtual directory on our live server, putting both .dll in the same bin
folder, and then only copying one of the web.config files and one
global.asax file to this "shared" virtual directory? Is that "legal" or
will that generate complications?

Thanks in advance!

Mark
"Cowboy (Gregory A. Beamer)" <No************@comcast.netNoSpamM> wrote in
message news:Oy**************@TK2MSFTNGP12.phx.gbl...

Not directly. You can fudge the global.asax by encapsulating the
functionality into a class library and calling the routines from each
global.asax. For the config, you are largely on your own, as configs work
for one project; the only solution I can think of is to create a separate
config type file.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

************************************************** ********************
Think Outside the Box!
************************************************** ********************
"Mark" <fi**************@umn.edu> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl...

I have two projects - they both need to use the same web.config file, the same global.asax file, and share a common "look and feel" via several user controls.

Is there an easy way for two projects to share these resources in VS.NET

so

we don't have to worry about synchronization issues ASIDE from combining

the

two projects into one?

Thanks in advance!
Mark