Our application consists of a suite of webservices. Depending upon
application area, different methods are grouped into separate webservice
projects, and are developed and maintained by separate development teams.
Let's assume for the sake of this discussion, that Team A, Team B and Team C
are working on separate webservice projects. (Ultimately, these separate
projects will integrate and comprise the entire application solution.)
Our webservice methods interoperate and maintain session state information
in the Session cache on the server. Naturally, webservice (asmx) pages
deployed to the same IIS virtual folder will share the same Session cache.
This means that as long as Team C has deployment artifacts for projects A
and B deployed to the same IIS virtual folder as Project C is mapped to,
then Team C is able to work on Project C in an environment which provides
the comprehensive application environment.
However, we have found that development is more convenient and projects are
more portable when the Visual Studio IDE, rather than IIS, is used to
function as the Web Server. We'd like to continue with this approach, but we
are finding that when multiple Projects are aggregated within a single
solution, each Project generates its own web server environment. In this
environment, the multiple projects do not share the same server environment
(e.g. Session cache) even though all projects are running concurrently
within the same solution. Is there any option to rectify this? Is there an
option to keep the projects isolated from IIS, to remain fully encapsulated
and supported within the IDE environment, yet at the same time specify that
all projects running within a single solution should share the same
server-side operating environment?
Thanks for your advice!
Joseph Geretz
application area, different methods are grouped into separate webservice
projects, and are developed and maintained by separate development teams.
Let's assume for the sake of this discussion, that Team A, Team B and Team C
are working on separate webservice projects. (Ultimately, these separate
projects will integrate and comprise the entire application solution.)
Our webservice methods interoperate and maintain session state information
in the Session cache on the server. Naturally, webservice (asmx) pages
deployed to the same IIS virtual folder will share the same Session cache.
This means that as long as Team C has deployment artifacts for projects A
and B deployed to the same IIS virtual folder as Project C is mapped to,
then Team C is able to work on Project C in an environment which provides
the comprehensive application environment.
However, we have found that development is more convenient and projects are
more portable when the Visual Studio IDE, rather than IIS, is used to
function as the Web Server. We'd like to continue with this approach, but we
are finding that when multiple Projects are aggregated within a single
solution, each Project generates its own web server environment. In this
environment, the multiple projects do not share the same server environment
(e.g. Session cache) even though all projects are running concurrently
within the same solution. Is there any option to rectify this? Is there an
option to keep the projects isolated from IIS, to remain fully encapsulated
and supported within the IDE environment, yet at the same time specify that
all projects running within a single solution should share the same
server-side operating environment?
Thanks for your advice!
Joseph Geretz
Comment