error parameterizing application pool identity

Hello,

There seems to be a bug in msdeploy when using it for parameterizing the application pool identity in combination with setting access rights through the setAcl provider.

In Visual Studio, we are using the following lines to parameterize the application pool identity:

<MsDeployDeclareParameters Include="Application Pool Identity – User Name">

      <Kind>DeploymentObjectAttribute</Kind>

      <Scope>processModel</Scope>

      <Match>processModel/@userName</Match>

      <Description>Please provide the User Name of the application pool</Description>

      <DefaultValue>mydomain\myuser</DefaultValue>

    </MsDeployDeclareParameters>

    <MsDeployDeclareParameters Include="Application Pool Identity – Password">

      <Kind>DeploymentObjectAttribute</Kind>

      <Scope>processModel</Scope>

      <Match>processModel/@password</Match>

      <Description>Please provide the Password of the application pool</Description>

      <DefaultValue>mypassword</DefaultValue>

    </MsDeployDeclareParameters>

We now want to give the application pool identity modify access on a certain directory:

     <MsDeploySourceManifest Include="setAcl">
        <Path>$(_MSDeployDirPath_FullPath)\MediaFiles</Path>
        <setAclAccess>Modify</setAclAccess>
        <setAclResourceType>Directory</setAclResourceType>
        <AdditionalProviderSettings>setAclResourceType;setAclAccess</AdditionalProviderSettings>
      </MsDeploySourceManifest>

When deploying and changing the application pool identity through -setParam arguments, the access rights are still given to the old application user (which results in an error when deploying to an AD domain without trust).

As a work around, I tried to parameterise the setAclUser, but without success:

      <MsDeployDeclareParameters Include="setacluser">
        <Kind>DeploymentObjectAttribute</Kind>
        <Scope>.*</Scope>
        <Match>//@setAclUser</Match>
        <Description>User to which to give access to directories</Description>
        <DefaultValue>conseur\SiteCoreApps</DefaultValue>
        <Value>mydomain\myUser</Value>
        <Priority>$(VsSetAclPriority)</Priority>
      </MsDeployDeclareParameters>

Am I doing something wrong? Could this behavior be improved in the next version of the Web Deployment Tool?

Notice that we are using some properties to include the application pool settings into the deployment package:

    <PackageAsSingleFile>True</PackageAsSingleFile>
    <IncludeIisSettings>True</IncludeIisSettings>
    <PackageEnableLinks>AppPoolExtension</PackageEnableLinks>