Closed tfabraham closed 6 years ago
[UnknownUser@3/4/2014] Resolved with changeset 74662: Provide enhanced control over AppDomains within BizTalk (#10542)
[tfabraham@3/6/2014] ** Closed by tfabraham 3/4/2014 12:02 PM
[UnknownUser@3/6/2014]
[UnknownUser@3/6/2014]
[UnknownUser@3/6/2014] Resolved with changeset 74670: Provide enhanced control over AppDomains within BizTalk (#10542)
[tfabraham@4/4/2014] ** Closed by tfabraham 3/6/2014 9:54 AM
[UnknownUser@4/4/2014]
[UnknownUser@4/4/2014]
[UnknownUser@4/4/2014] Resolved with changeset 74812: Absolute path conversion and error handling for BizTalkAppDomain (#10542)
[tfabraham@4/4/2014] ** Closed by tfabraham 4/4/2014 9:39 AM
[UnknownUser@4/4/2014]
[UnknownUser@4/4/2014]
[UnknownUser@4/4/2014] Resolved with changeset 74813: Remove existing items from AppDomainSpec XML when not present in btdfproj (#10542)
It has long been possible to instruct BizTalk to load your application's assemblies into a separate .NET AppDomain that does not interact with any other running BizTalk apps. The Deployment Framework has supported automatic configuration of that feature for many years, but did not expose one of the most important settings -- an AppDomain-specific .NET configuration file path. Need to configure Enterprise Library or store custom settings for a single app without modifying BTSNTSvc.exe.config? This feature is for you.
Add a new BizTalkAppDomain ItemGroup that allows one or more AppDomains to be configured for an app, and exposes explicit and regex-based assembly name assignment into those AppDomains. Also expose several of the most useful properties of the AppDomainSetup class including ConfigurationFilePath and ApplicationBase.
This work item was migrated from CodePlex
CodePlex work item ID: '10542' Assigned to: 'tfabraham' Vote count: '1'