Merging 2 asp.net web applications.

[hmgblr]

Hello,

Right now, we have 2 different web applications SiteA and SiteB. SiteA is our companies main and existing web app. We created SiteB, a new site (with it's own virtual directory). For Biz sake, SiteA being our main web site, the newly created web site (SiteB) should appear under SiteA (basically content or resources in SiteB should appear under SiteA].

So the current url paths look like this:

Site A:

http://samplesite/SiteA/Home.aspx

[main web site home page]

Site B:

http://samplesite/SiteB/Stuff/Home.aspx

[newly created sites home page].

I would like the following scenario when a User tries to acccess 'SiteB's home page

Expected behavior:

http://samplesite/SiteA/Stuff/Home.aspx

I tried merging two different webapplications into one, but ran into plenty of resource conflicts. I also tried URL rewriting, but was not able to give an alias for 'SiteB' to 'SiteA'.

Please let me know of a solution. Appreciate all the help!

 

[Kalisto]

Ok, before anyone flames me Im thinking out loud, Im not an IIS admin ;-)

If the folder "Stuff" does not exist in Site A, then you wont be able to display anything in it. IIS will look for that folder (even if you are url rewriting with a http module), and if it doesnt exist serve up an error message.

In effect I think you are trying to do cross site scripting, which is disapproved of as this is often a way that sites can be attacked.

Its a fudge, and might not do what you need, but could you create a folder in Site A's structure, and have a page that contains nothing but an IFrame that points to B?

Or would creating a sub domain and changing the http headers in the webserver work (i.e. have

http://www/SampleSite/Home.aspx

and

http://SampleB/SampleSite/Home.aspx)

I think that ultimately though, if you have a business case for merging the 2 sites together, then you will be better off resolving your resource conflicts as you wil then have less to manage. At present, if the shared resource is updated on one site, you run the risk of breaking the other site, or having to manage multiple versions of your files.