There are quite a few blog entries out there about sharepoint and applications hosted on the same machine.
There is a KB article on it too http://support.microsoft.com/?id=823265. You modify the managed paths.
Well true this works and apps can run side by side, in fact you can run applications inside sharepoint with the managed paths option. We did hit some problems in doing this.
- All of a sudden Session stopped working, it told us hey turn it on. Well I can tell you it was turned on. Nevr got round to fixing this, if someone knows of the problem and of a fix post a comment.
- Visual Studio became a bloody nightmare. Whilst it could create new apps apps opened from Sourcesafe had a blue fit.
So we tried to install Sharepoint and Apps on two seperate webs. We also utilised host-headers so both webs could use port 80. This does require the developers box to be Server 2003. If you have one monitor, then dont do it virutalise it and have seperate boxes. If you have two monitors you will lose productivity by not doing it, but be prepared to re-install sharepoint, beter still make a copy of everything to copy over the top of your customisations that have gone wrong, and they will go wrong.
Did it work. Did it “eck as like”. Visual Studio bitched about it again. Why ? becuase of the way Studio enumerates the webs to determine which is the Default Web (ie the one you dont want sharepoint on).
Even though our SPS or WSS install was on a http://scarepoint host-header, and we were opening localhost. Studio got it wrong.
We believe overcame this, (well I think we did, havent repeated this installation yet ).
After Sharepoint has been installed, create a NEW web, this will point at the default web. give it all the same settings as default web then delete default web (you may need to modify default web settings to set the new ones).
Now when you do things in studio, it enumerates the webs and takes the NEWEST web as its default. This is what APPEARS to happen not being the studio developers we dont know for sure.
Now it all works, no mananged paths, no session problems interface into sourcesafe nicely.
Thanks to my colleague Mark Sheppard for finding this one, I think he got fed up with my profanity so had to fix it quick.
DO NOT DO THIS UNLESS YOU ARE PREPARED TO HAVE IT GO WRONG AND YOU NEED TO REBUILD. DO THIS AT YOUR OWN RISK.