Switch between 'Local Development' and 'Shared Development' environment settings - BTDF/DeploymentFramework GitHub Wiki
Wiki: Home > Tips and Tricks
Requirement
Most of the time when developing with BizTalk, you want to isolate your dependencies on external systems and services. So you stub them out to work in a localised way.
However, every so often, you still need to connect to real (dev\test) instances of the source and target endpoints\services. For example, you may need to:
- (Re)generate a schema.
- You may be asked to send a message to see if everything still works.
- You might want some messages sent to BizTalk to get confidence that everything still works.
Solution
The BTDF environments spread sheet out-of-the-box gives you two development environments:
Environment | Purpose |
---|---|
Local Development | Work in a localised environment - external systems are stubbed. |
Shared Development | Work with client\service developers - point to their developer endpoint instances. |
In order to switch between the two environments, add the following to your .btdfproj file.
<!-- Un-comment this line to use the shared developer settings -->
<!-- <DeveloperPreProcessSettings>$(MSBuildProjectDirectory)\EnvironmentSettings\Exported_DevSettings.xml</DeveloperPreProcessSettings> -->
References
- Original Source: https://biztalkdeployment.codeplex.com/discussions/353808
- Dealing with external systems/dependencies: http://geekswithblogs.net/michaelstephenson/archive/2009/05/12/132052.aspx