I'm wondering if anyone can point me at the best practices for installing a complex service (basically, an entire web application) into SP when doing a feature install.
We have an existing web application that we'd like to package into a WSP. The application is a set of ASMX web services that are used by the web parts that make up the "meat" of the feature. It also has some ASPX pages for administration purposes.
The problem is that this web app depends on a lot of low-level infrastructure such as http modules & handlers, new DLLs, etc. It has its own web.config with app settings, etc. and as such doesn't fit in well as a drop-in to the _layouts directory, which is where I'd normally put our custom pages.
I see that in 2010 there seems to be some sort of "SP Service Provisioning" classes, which might let me install something into IIS, etc. But I'm not sure that's the right direction, and in any case I need to do this for SP2007.
So... anyone have any opinion about the best way to use WSP feature installation to basically install an entire new web app, or vdir within SP?
[Please let me know if I need to clarify anything - I might not have explained it well]