Want to confirm: is it OK to put more than 1 assemblies into one I

Thanks for everyone repying.
Have new thoughts here.
1. Comboapps actually does not have associated assembly; it's just an IIS
application. How can I have global.asax facilities?
2. If I have to create a very small assembly for the Comboapps, is there any
easy to debug the code in global.asax?
Thanks.
"Edward Yang" wrote:

> In my test, I have two web applications app1 and app2, and I configure
> them as follows in IIS:
> $/comboapps
> |--web.config
> |--bin
> | app1.dll
> | app2.dll
> |--app1
> | form1.aspx
> | web.config
> |--app2
> | form1.aspx
> | web.config
> (Of course, I have to remove authentication, authorization, sessionstate
> tags from web.config in app1 and app2.)
> In this way both apps share the same session because they are in one IIS
> application.
> Things work well for me so far. But I have some uncertainties:
> 1. What should I do with each global.asax file in app1 and app2?
> 2. Is this method supported by Microsoft (I can't draw a conclusion by
> reading documentation)?
> 3. What is the logic of Configuration.AppSettings("somename") in the
> above scenario? Does the Framework check the web.config in app root first?
> Great thanks if someone can sort my head out for a bit.
>re:
> 1. Comboapps actually does not have associated
> assembly; it's just an IIS application. How can I have
> global.asax facilities?
You don't need to have an assembly in order to have an IIS Application.
If /comboapps is an IIS Application, it can use a global.asax.
re:
> 2. If I have to create a very small
> assembly for the Comboapps
You don't have to.
Just make sure /comboapps is an IIS Application,
write a global.asax file in the app's roots dir, and
declare whatever you want to declare in it.
ASP.NET will recognize/execute it.
Juan T. Llibre
ASP.NET MVP
===========
"Neo The One" <NeoTheOne@.discussions.microsoft.com> wrote in message
news:CE3AD4A1-8A48-40DC-83BF-ED3CA929C45D@.microsoft.com...
> Thanks for everyone repying.
> Have new thoughts here.
> 1. Comboapps actually does not have associated assembly; it's just an IIS
> application. How can I have global.asax facilities?
> 2. If I have to create a very small assembly for the Comboapps, is there
> any
> easy to debug the code in global.asax?
> Thanks.
> "Edward Yang" wrote:
>