Sharing session between two asp.net apps.

But what on earth has an application with 200 aspx files? Explain it to me
because I do not get it. Without your explanation, i suggest you look into
master templates and user controls to cut down on the size of this monster.
Do you really expect that application to fit nicely on a page of memory?
That should be your target otherwise you incur soft as well as hard page
faults which means your application will run as fast as turtles do.

"Rajesh.V" <Rajesh_vanchi@dotnet.itags.org.hotmail.com> wrote in message
news:ezo8vngkDHA.1284@dotnet.itags.org.TK2MSFTNGP09.phx.gbl...
> As many of you know this is a legitimate requirement. As once the no of
aspx
> pages pages in a project increase - say to around 200 on dev machine piii
> 500, 256 mb memory. The cpu util stays at 100% for some time and
compilation
> takes a lot of time, not to talk of debugging. Team development is
> impossible without vss and some person spending solely on integrating. So
it
> would be better to split it into sub applicaitons, which will increase the
> reliability. Also multiple teams can work on it.
> Now to this post previously i got various replies.
> 1. From Natty Gur - Use mms(shared memory), which is complicated (at least
> for me :-}. -- Fast but tied up with win32 dll.
> 2. Xiangyang Liu - Use Remoting and use custom db to store the session
> variable and data. -- Slow
> http://www.codeproject.com/aspnet/sessiontool.asp
> 3. Use Web service - Too slow
> Now one of my friends picked this one out of msdn
> http://support.microsoft.com/defaul...Ben-us%3B307467
> This needs some effort during integrating, after the individual Asp.net
apps
> have been tested out. This seems to the solution of the hour and optimum.
> I wonder how many of you Asp.Net developers out there have used this and i
> would like to know whether it works fine.
> Rajesh.VTo say the truth, its not my application but a guy who posted that he had
700 pages. Again my suggestion to him was there is something seriously wrong
with the design. But he stuck to the guns. This was 4 months ago. But i
still needed a solution with multiple asp.net apps sharing the same session.

But seriously considering some of companies i am working with, they are
turning out all sorts of apps to web to escape installation problems and
security. They do have this much forms where each form is unique, no amount
of templating or usercontrols are goin to solve that problem.

So are u using Parent/child asp.net apps...

"Alvin Bruney" <vapordan_spam_me_not@.hotmail_no_spamhotmail.com> wrote in
message news:O5YL$iokDHA.988@.TK2MSFTNGP10.phx.gbl...
> But what on earth has an application with 200 aspx files? Explain it to me
> because I do not get it. Without your explanation, i suggest you look into
> master templates and user controls to cut down on the size of this
monster.
> Do you really expect that application to fit nicely on a page of memory?
> That should be your target otherwise you incur soft as well as hard page
> faults which means your application will run as fast as turtles do.
> "Rajesh.V" <Rajesh_vanchi@.hotmail.com> wrote in message
> news:ezo8vngkDHA.1284@.TK2MSFTNGP09.phx.gbl...
> > As many of you know this is a legitimate requirement. As once the no of
> aspx
> > pages pages in a project increase - say to around 200 on dev machine
piii
> > 500, 256 mb memory. The cpu util stays at 100% for some time and
> compilation
> > takes a lot of time, not to talk of debugging. Team development is
> > impossible without vss and some person spending solely on integrating.
So
> it
> > would be better to split it into sub applicaitons, which will increase
the
> > reliability. Also multiple teams can work on it.
> > Now to this post previously i got various replies.
> > 1. From Natty Gur - Use mms(shared memory), which is complicated (at
least
> > for me :-}. -- Fast but tied up with win32 dll.
> > 2. Xiangyang Liu - Use Remoting and use custom db to store the session
> > variable and data. -- Slow
> > http://www.codeproject.com/aspnet/sessiontool.asp
> > 3. Use Web service - Too slow
> > Now one of my friends picked this one out of msdn
> > http://support.microsoft.com/defaul...Ben-us%3B307467
> > This needs some effort during integrating, after the individual Asp.net
> apps
> > have been tested out. This seems to the solution of the hour and
optimum.
> > I wonder how many of you Asp.Net developers out there have used this and
i
> > would like to know whether it works fine.
> > Rajesh.V