New Post: Deploy solution on development system

I see -- the Standard edition app limit is a big pain. I looked into this some more and have something for you to try. By default, the Deployment Framework still undeploys an app piece by piece except for BRE policies. As a result, I believe that the app delete/add is really not important to the overall process.

Try putting this into the .btdfproj for the app that is the default app (this is untested):

<Target Name="DeployAppDefinition" DependsOnTargets="VerifyBizTalkAppExists">
  <Exec
    Command="BTSTask.exe AddApp -ApplicationName:&quot;$(BizTalkAppName)&quot; -Description:&quot;$(BizTalkAppDescription)&quot;"
    Condition="'$(AppExists)' == 'false'" />
  <AddAppReference
    ApplicationName="$(BizTalkAppName)"
    AppsToReference="@(AppsToReference)" Condition="%(Identity) == %(Identity) and '@(AppsToReference)' != '' and '$(AppExists)' == 'false'" />
</Target>

<Target Name="UndeployAppDefinition" Condition="'$(SkipUndeploy)' == 'false'" DependsOnTargets="PrepareAppForUndeploy">
</Target>

This overrides the default targets of the same names. It should still create the app if it doesn't exist, but should never delete the app once it exists.

If you have BRE policies, you should also add the property RemoveRulePoliciesFromAppOnUndeploy set to True.

Thanks,
Tom