Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update and delete iis artifacts in v5.7 does not seem to work. #449

Open
saaffy opened this issue May 30, 2018 · 1 comment
Open

update and delete iis artifacts in v5.7 does not seem to work. #449

saaffy opened this issue May 30, 2018 · 1 comment

Comments

@saaffy
Copy link

saaffy commented May 30, 2018

I want to be able to undeploy my MSI and let the BTDF delete the virtual dir. Though the setting UndeployAction is set to Delete, undeploying does NOT remove the virtual dir (only the folder /solution_1.2.3_ on disk)
Also, if I then install a newer version of the same solution, I would expect that the still existing virtual dir gets mapped to the new version folder /solution_1.2.4_). But instead the virtual dir is mapped on the old (removed) folder.

These are my settings ....

<!-- IIS AppPools-->
  <ItemGroup>
    <IISAppPool Include="BiztalkAppPool">
      <DeployAction>Create</DeployAction>
      <DotNetFrameworkVersion>v4.0</DotNetFrameworkVersion>
      <Enable32Bit>false</Enable32Bit>
      <IdentityType>ApplicationPoolIdentity</IdentityType>
      <PipelineMode>Integrated</PipelineMode>
      <UndeployAction>None</UndeployAction>
    </IISAppPool>
  </ItemGroup>

  <ItemGroup>
    <IISApp Include="XXXX.YYYYY">
      <AppPoolName>BiztalkAppPool</AppPoolName>
<Exclusions>*.csproj;Web.Debug.config;Web.Release.config;WcfServiceDescription.xml;obj;Properties</Exclusions>
      <DeployAction>CreateOrUpdate</DeployAction>
      <PhysicalPath>..\XXXX.YYY.PATH</PhysicalPath>
      <SiteName>Default Web Site</SiteName>
      <UndeployAction>Delete</UndeployAction>
      <VirtualPath>/XXXX.YYYYYYYY</VirtualPath>
    </IISApp>
  </ItemGroup>
@tfabraham
Copy link
Member

"undeploy my MSI" doesn't make sense. You must execute the undeploy, then uninstall the MSI, then install the new MSI, then execute the deploy. If you are just uninstalling the MSI, then all of the artifacts will remain in BizTalk and IIS. Are you executing the undeploy process before uninstalling the MSI?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants