MSBuild wpp.targets file to fix the long path in web packages from Visual Studio

fix-package-path.wpp.targets

<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="12.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <PropertyGroup>
    <PackagePath Condition=" '$(PackagePath)'=='' ">website</PackagePath>
    <EnableAddReplaceToUpdatePacakgePath Condition=" '$(EnableAddReplaceToUpdatePacakgePath)'=='' ">true</EnableAddReplaceToUpdatePacakgePath>

    <PackageDependsOn>
      $(PackageDependsOn);
      AddReplaceRuleForAppPath;
    </PackageDependsOn>
  </PropertyGroup>

  <Target Name="AddReplaceRuleForAppPath" Condition=" '$(EnableAddReplaceToUpdatePacakgePath)'=='true' ">
    <PropertyGroup>
      <_PkgPathFull Condition=" '$(WPPAllFilesInSingleFolder)'!='' ">$([System.IO.Path]::GetFullPath($(WPPAllFilesInSingleFolder)))</_PkgPathFull>
      <_PkgPathFull Condition=" '$(_PkgPathFull)' == '' ">$([System.IO.Path]::GetFullPath($(_PackageTempDir)))</_PkgPathFull>
    </PropertyGroup>

    <!-- escape the text into a regex -->
    <EscapeTextForRegularExpressions Text="$(_PkgPathFull)">
      <Output TaskParameter="Result" PropertyName="_PkgPathRegex" />
    </EscapeTextForRegularExpressions>
    
    <ItemGroup>
      <MsDeployReplaceRules Include="replaceFullPath">
        <Match>$(_PkgPathRegex)</Match>
        <Replace>$(PackagePath)</Replace>
      </MsDeployReplaceRules>
    </ItemGroup>
  </Target>
</Project>

@jeremy-jameson thanks for letting me know. I don't see why this would cause that behavior. Do you have any ideas?

Can you make the sample packages you created available so I van download them? That will simplify my investigation.

@jeremy-jameson @sayedihashimi I wrote about this here including a sample project https://code.msdn.microsoft.com/Updating-MsDeployParameters-33b5ee93

The cause of the problem is that in the parameters.xml file, the scope attribute of the parameterEntry element still contains the long path to the original location, so it expects the web.config file to still be there. I have not tried it yet, but I believe changing the scope attribute to website\\Web\.config$ would fix it.

Is it intentional that the EnableAddReplaceToUpdatePacakgePath has Pacakge instead of Package..