- UK: +44 (1689) 666 575
- US: +1 (855) 867-8251 (Toll Free)
You can deal with the dependencies between BizTalk artifacts through the different options available in the add-in.
Perform a full textual search across all the artifacts within your solution. This is very similar to making a search inside a single artifact with the Visual Studio search feature, but the add-in extends the search across all the artifacts in your solution.
Reporting capabilities with information such as statistics, solution & artifact metrics, artifact dependencies, number of shapes in the orchestration, and so on. The reports are also interactive – you can open the artifacts as you read the reports!
When your solution file is huge with lots of projects, building a single project can get time consuming, given the internal dependencies between projects. With the add-in, you have the option of building only the required project.
How many times have you thought of having an easy way to register/unregister a DLL into GAC. This is now possible with BizTalk NoS through register/unregister in GAC functionality. You can now do this through the Visual Studio window.
Deploy a BizTalk assembly directly from the bin directory in Visual Studio. This is very similar to adding/updating a resource from the BizTalk server administration console.
Similar to testing a pipeline, you can now test a custom pipeline component through Visual Studio. In just 2-3 steps, you can configure and test (debug) your pipeline component.
You’ve the option to test your pipeline right within the Visual Studio developer environment. You need not use a separate BizTalk Pipeline Framework or use the Pipeline.exe tool anymore!
With BizTalk NoS, you can jackhammer BizTalk in order to compare the artifacts in your development environment with that in production. It’s a very useful feature for BizTalk developers & administrators.
Creates a more simple report with circular (internal & external) references with other artifacts. You will receive a detailed statistic information about who’s using the artifact, which other artifacts is the current artifact consuming, and so on.
Back to Top