Orchard installation as root on IIS with other applications not working.

Topics: General, Installing Orchard
Apr 23, 2015 at 11:49 PM
We are implementing Orchard and trying to integrate our new Orchard site with other web applications our company uses. One such application is a webstore package. We simply want to add a menu item called webstore and have the URL point to the webstore application. This isn't working and I believe it is because of the routing with Orchard as the route. It doesn't know about the webstore as a route so when the url is typed in, it says (inside orchard) can't find the page.

Here is our setup:
Orchard installed on http://test.companyname.com
virtual directory was added that points to the application folder for webstore. So that path would be http://test.companyname.com/webstore.

Again, I'm pretty sure this is a routing problem because if I type the actual path of the webstore into the menue item URL (http://webtest.companyname.com/store) it will work. Since it isn't going through the Orchard path.

Any ideas on how to change the route or other ideas on how to make this work.
Coordinator
Apr 24, 2015 at 12:29 AM
If it's a separate application, why do you expect Orchard to be able to use its routes? What URL did you enter in the menu item?
Apr 24, 2015 at 1:25 AM
Edited Apr 24, 2015 at 1:25 AM
Our Orchard site should be available at http://www.companyname.com, which it is. Our goal and the way we are targeting the integration with the base url and to access the store should be http://www.companyname.com/store. Now in IIS, we have store added as a virtual folder. That is why I'm thinking the route needs to be changed because inside the orchard implementation, /store does not exist and it returns a page not found message. We basically want everything to reside under the base url but it isn't clear how to get orchard to allow for other paths.
Apr 26, 2015 at 2:57 PM
Edited Apr 26, 2015 at 2:58 PM
Marked as answer by n2teeth on 4/27/2015 at 3:52 PM
Developer
Apr 26, 2015 at 4:39 PM
Edited Apr 26, 2015 at 4:40 PM
n2teeth wrote:
Our Orchard site should be available at http://www.companyname.com, which it is. Our goal and the way we are targeting the integration with the base url and to access the store should be http://www.companyname.com/store. Now in IIS, we have store added as a virtual folder. (...)
Sounds like a perfect scenario for using URL rewrite rules. Simply rewrite everything that comes to /store URL to the second application (which can be set up anywhere, not necessarily in a virtual subfolder - making this less problematic).
Apr 27, 2015 at 11:52 PM
Thanks for the responses. I ended up finding the following on SO and was able to piece a fix together for the moment. I also ran into the css styling issue so the part that isn't referenced as the solution but just underneath it really helped as well. to bad two solutions can't be marked.

Some of the external links are no longer valid but this will definitely help to find the answer. http://stackoverflow.com/questions/9369625/virtual-directory-inside-orchard-web-application