Visual Studio Publish Publish When Adding ACL for Path

I am trying to publish a web application, but it has stuck the last 10 minutes in the Adding ACL for path . I do not know why he was stuck there, I published several times without any problems.

+9
visual-studio webdeploy
source share
3 answers

I had the same problem and it turned out that in the deployed web application a lot of user-specific directories and files were accumulated in the user directory for downloads / report files, etc. Visual Studio checks and updates access control lists for each file and directory, and therefore it takes a lot of time if there are a lot of them.

Check directories with a huge amount of user content or other content with a large number of files and check if you can safely delete them (for example, if these files are created only temporarily - as it was in this case).

After cleaning the directory on the web server, the deployment is almost instantaneous for incremental updates, which were very slow before the cleanup process.

+13
source share

It seems you have too many files and it takes a lot of time. I solved this problem by adding the following line to the .pubxml file.

 <IncludeSetACLProviderOnDestination>False</IncludeSetACLProviderOnDestination> 
+3
source share

First, upload your project (right-click on the project and find the unload project), and then open the .pxxml file and add

 <IncludeSetACLProviderOnDestination>False</IncludeSetACLProviderOnDestination> 

under

  <PropertyGroup> 

which should look

 <?xml version="1.0" encoding="utf-8"?> <!-- This file is used by the publish/package process of your Web project. You can customize the behavior of this process by editing this MSBuild file. In order to learn more about this please visit http://go.microsoft.com/fwlink/?LinkID=208121. --> <Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003"> <PropertyGroup> <IncludeSetACLProviderOnDestination>False</IncludeSetACLProviderOnDestination> 
0
source share

All Articles