Visual Studio 2010 web deployment projects do not remote the App_Data folder

Having come accross the problem before that Visual Studio 2010 web deployment projects do not remote the App_Data folder even though you have checked the box to do exactly that I have today found myself trying to find what the resolution was again so thought I would blog about it partially for your benefit but also for my own sanity should I need this information again.

Open the file
C:\Program Files (x86)\MSBuild\Microsoft\WebDeployment\v10.0\Microsoft.WebDeployment.targets

Locate the following section and add in the missing red backslash

        <!--
        Removing APP_DATA is done here so that the output groups reflect the fact that App_data is
        not present
        -->
        <RemoveDir Condition="'$(DeleteAppDataFolder)' == 'true'" Directories="$(TempBuildDir)\App_Data"/>
        <CreateItem Include="$(TempBuildDir)\**\*.*"  Condition="'$(UseMerge)' != 'true'">
            <Output ItemName="PrecompiledOutput" TaskParameter="Include" />
        </CreateItem>

Comments

Post a Comment

Popular posts from this blog

SOLVED: Exchange Online Management PowerShell Connect-ExchangeOnline bug "A window handle must be configured. See https://aka.ms/msal-net-wam#parent-window-handles"

Image
This post has been updated here: https://www.centrel-solutions.com/blog/exchange-online-powershell-window-handle-error While you're here why not check out our  Exchange audit and documentation tool ? If you're using the Exchange Online Management PowerShell cmdlets you may notice that the following error: A window handle must be configured. See https://aka.ms/msal-net-wam#parent-window-handles This error appears in version 3.7.0 (and persists in version 3.7.1) when the following change was made. Integrated WAM (Web Account Manager) in Authentication flows to enhance security. You notice that this error occurs in PowerShell ISE but not in a PowerShell, the issue also appears in any Windows based applications - for example a WinForms application that tries to execute Connect-ExchangeOnline PowerShell ISE A .NET console application does work correctly. .NET console application While you're here why not check out our  Exchange audit and documentation tool ? The error occurs be...
Read more

System error 86 has occurred. The specified network password is not correct.

Image
Network Audit and Documentation     Sometimes we forget about some of Microsoft's very annoying "helpful" additions. This is one I just got stuck on when trying to access a UNC share you are constantly prompted for a username and password. When you try to map a network drive you receive the following error System error 86 has occurred. The specified network password is not correct. After a while of trying to remember what this meant, I realise this is the following option in Folder Options. Use simple file sharing (Recommended) I'll add this to the ever so painful "Desktop Cleanup Wizard" and the forthcoming Metro user interface.
Read more

The security identifier of the "NT SERVICE\WdiServiceHost" account is "S-1-5-80-3139157870-2983391045-3678747466-658725712-1809340420"

This week we have been working on support for PCI-DSS and CIS compliance auditing. One of the CIS server requirements is to ensure that the following is configured 2.2.34 Set 'Profile system performance' to 'Administrators, NT SERVICE\WdiServiceHost' (Scored) Rather than code string values into the product (which can cause problems with foreign language operating system installations) we use the well known security identifiers of these built in accounts. The security identifier of the "NT SERVICE\WdiServiceHost" account does not appear to be documented (well not easily found anyway) so here it is. The security identifier of the "NT SERVICE\WdiServiceHost" account is "S-1-5-80-3139157870-2983391045-3678747466-658725712-1809340420" This has been tested on Windows Server 2008 R2 Windows Sever 2012 Windows Server 2012 R2 Windows 10
Read more