Web Deployment Tool (MS Deploy)
targets file documentation (publishing from Visual Studio)
Last post May 24, 2012 09:42 AM by dirq
May 22, 2012 11:55 AM|dirq|LINK
May 24, 2012 04:23 AM|Lloydz|LINK
How do I set anonymous access on a folder within a windows authenticated IIS7 site?
This could be easy to accomplish after you have published your application. Open IIS manager, click the site, click the folder you need to enable anonymous authentication, double click Authentication feature, enable anonymous authentication. If you are not
familiar with these steps, you can simply add the following section into your folder web.config which will accomplish the same:
<anonymousAuthentication enabled="true" />
How do I exclude folders for publish while making sure they exist in the target site after installation (e.g. an uploads folder)?
You may take reference to the following blog entry for excluding folders for publishing:
Web Deployment: Excluding Files and Folders via the Web Application’s Project File
For your first question, I believe there's no blog entry could cover all your questions. You may search specific ones through internet, or post the exact questions in the forums, the community would be strong enough to help.
May 24, 2012 09:42 AM|dirq|LINK
Thanks a bunch Lloydz!
I found that in order to override IIS 7 authentication settings within a website (via the web.config), you first have to allow overrides in the applicationHost.config file. For others reading this post, this article has info on how to do that:
Thanks for the help on the other topics. It really would be great if Microsoft improved the documentation for this area. Especially what the targets file can do with the web deploy publish tool in Visual Studio. It seems to be really powerful and I know
that a lot of developers don't know much about it. Documentation would help to get the word out.
It would also be completely awesome to have a way to clear Visual Studio's cache of the targets file. Since the documentation is limited, and the errors uninformative, it takes a ton of trial and error to get the targets file setup to do what you want.
Rebooting VS to read changes is a royal pain.