Well I’ve done that SPS build to another machine now and all seems well.
I had a combined SPS/WSS and Application installation. WSS install was to my default web which had loads of existing applications in it. I had manged paths in sharepoint to to make this work in this scenario. My wwwroot folder was on drive D: also so my changes reflect this.
So Heres exactly what I did.
Had some problems with stsadm not working against my sites whan adding a webpart, this is because I created my portal before the host-header rename. So before you do this to enable it to work you have to DELETE ALL SITES, than after this Create a new SPS site. (The same probably applies to WSS as well)
The best approach is to have all the Virtual Webs in place before installing WSS/SPS, but admittedly I havent tried this installation yet so cant advise on it, I will have to soon when I get some new more powerful kit. My 1.4mhz processor is creaking a little under all this strain.
- Create a new folder d:intepubwwwscarepoint
- Copy the aspnet_client script folder into it (not sure if needed, but safe than sorry)
- Copy the Web.config file from other wwwroot into here.
- In IIS change default web home directory folder to scarepoint folder (this is the Virtual web that has sharepoint installed in it, if you installed it elsewhere dont do it to default web, infact if you did it elsewhere you probably solved this problem anyway).
- Rename the Default Web Sharepoint (aethetics)
- Remove any Virtual Directories you have in here that you no longer want in here, take care IIS deletes can delete the source too not just the VD. Cant rememeber what circumstances though.
- For the Sharepoint IP address add a host-header for port 80 I used Scarepoint
- If you have control over your dns then enter an alias for your scarepoint url, if you dont you can put one in the hosts file for 127.0.0.1. (If you don’t know how to do this, why are you in web development again ? )
- Create a new WEB and call it Default Web, point it at your wwwroot folder, ensure you have the correct Application Pool.
- Reset the directory security you want
- Add any additional default documents you may have
- In the wwwroot folder return your web.config to its original state, minus sharepoint settings ! (This made my Session problems go away).
And thats all, everything seems to work now, sharepoint, my apps, and most importantly Visual Studio/IIS integration.
DO NOT DO THIS UNLESS YOU ARE PREPARED TO HAVE IT GO WRONG AND YOU NEED TO REBUILD. DO THIS AT YOUR OWN RISK.