If you want to simply host this web site beneath the same URL as MOSS 2007, you can add a "managed path" in SharePoint that you mark as "excluded" in Central Administration (a simple Bing search should turn up how to do that). Then create a folder on the server to drop your application, and map a virtual folder in IIS using the managed path you defined, mapped to the physical folder you just created. If you want to host your application within SharePoint, you really need to convert it to a format that will work in SharePoint. There you have the choice between application pages (.aspx pages that are available in any SharePoinbt site, like those in Site Settings), or if your site is mainly static html then you could use either web part pages (more appropriate for a one-off site simply to host content)or a publishing site with page layouts (more appropriate if you want to version your pages or want to maintain a consistent format, as with news articles or product information). If this is an ASP.NET app with many .aspx pages and you don't want to convert it, consider just using a Content Editor Web Part with an IFRAME in it to surface your application in some SharePoint site. And as a final option, if your application is a well-designed 3-tier application, then it shouldn't be hard to rewrite as web parts. The usual problem is that inexperienced developers often jam both the UI and logic together making it difficult to tease back apart, so the conversion to web parts or application pages becomes more like a rewrite than a simple re-skinning of all the capabilities that should reside in a logic layer. Hope this gives you a few ideas to get started. Cheers, -Eli.
