Unfortunetly the aspnet_regiis -sn path option refers an IIS virtual directory not its associated mapped file path. And as far as I've ever been able to find out the VS.Net web deployment project is that its fairly worthless because you cannot specify a website AND a web application to deploy the application files to just an application. So what you end up doing is using the standard deployment project which is a file path based deployment. Like an XCopy deploy really. This means that when you go to run the utility from the Installer class the virtual directory mapped to the physical directory that you're dropping the files in is unknown ... I think. The only things you can do I think are: 1. Buy something like InstallShield. Question. Does it handle installation into multiple web sites? If so you could likely obtain the virtual directory's path at install time. 2. Somehow figure out the IIS vitual path designation for the web site and application that maps to the physical file path that you're deploying the files to. Is there a way to do this? I know I can script some of this but doing a lot of this could get messy fast. I'm I wrong on any of these points?
=================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: Essential .NET: building applications and components with CSharp August 30 - September 3, in Los Angeles http://www.develop.com/courses/edotnet View archives and manage your subscription(s) at http://discuss.develop.com
