Open tfabraham opened 6 years ago
[UnknownUser@3/21/2014] Associated with changeset 74749: Start app after restarting host instances; enable granular control over app start/stop (#10565; #10562)
[UnknownUser@3/28/2014] Associated with changeset 74781: Enable granular control over app start/stop (#10562)
[UnknownUser@3/28/2014] Resolved with changeset 74787: Deploy shared assemblies before SSO (#10562)
[tfabraham@3/28/2014] ** Closed by tfabraham 3/28/2014 3:12 PM
[UnknownUser@3/28/2014]
[UnknownUser@3/28/2014]
[UnknownUser@8/20/2017]
The Deployment Framework currently uses the BizTalk ExplorerOM Application Start() and Stop() methods, just like BizTalk Admin. In some situations a developer may want very granular control over starting or stopping an application. For example, enabling only certain receive locations or send ports, etc.
This feature adds a number of new ItemGroups that allow such granular control. The Deployment Framework automatically discovers all instances of each artifact housed within the application and follows a default behavior for each one. Those defaults may be overridden in the .btdfproj as needed.
For example (not final):
This work item was migrated from CodePlex
CodePlex work item ID: '10562' Assigned to: 'tfabraham' Vote count: '2'