Concerning best practices:
1. Is it ok to have a setup like below if Test web is not running SharePoint, or is there a better way to configure non SharePoint virtual directories running on a SharePoint portal server? Name URL Version
Default Web Site http://spsweb01/ 6.0.2.8117
Test http://spsweb:8080/ Not Installed Extend Actually - I would rather not even see these non SharePoint webs using SharePoint admin tools, but I couldn’t see a way to exclude the path since it’s not part of SharePoint. 2. Are there any reasons why I should not change my default SharePoint Portal web to use ASP .Net 2.0 (as long as 3rd party web parts don't break)? 3. Finally, if the answer to 2 is: No, I should not change it, then are there any issues running a non SharePoint virtual directory web using 2.0 as long as that web uses a different application pool?
Thanks... Marc