I am using the IIS7 task to setup websites and applications on a remote server and I run into one of two issues depending on which type of path I provide. If I use a path that contains the computer name, \\webserver\some\path for example, IIS and .NET complain about security permissions. If I use a path that is local to the web server, F:\some\path for example, the IIS7 tasks return an error saying that part of the path could not be found. Commenting out the blocks of code that check if the directory exists and creates it if it doesn't stops the error.
So I was thinking that the task should check if the specified machine name is local, and if it's not, don't do the directory checking. I'll make the change and submit it if that sounds like a reasonable approach.
Comments: ** Comment from web user: MarkusWolff **
So I was thinking that the task should check if the specified machine name is local, and if it's not, don't do the directory checking. I'll make the change and submit it if that sounds like a reasonable approach.
Comments: ** Comment from web user: MarkusWolff **
I've got a similar problem. If I use a path like this \\webserver\f$\some\path my Build tasks works OK but the configured application throws an exception. When I look at the application's configuration in IIS Manager it uses the exact same path. As soon as I changed it to f:\some\path the application works fine again. Why can't I use this path in my MSBuild project in a remote setup?