You work as a Microsoft BizTalk Server 2006 Developer for Domain.com. The development of Integration applications is your responsibility at Domain.com. You received instruction to build and deploy a custom pipeline assembly.
You have a solution that includes your custom pipeline project and your BizTalk application project that uses it.
Each time you attempt to build your custom pipeline project, or rebuild your solution, you receive an error stating that the output dll is being used by another process. You need to complete your task of building and deploying the custom pipeline assembly and need to take a decision as to the appropriate action to take.
What should you do?
A.
You should reinstall Microsoft BizTalk Server 2006 as your BizTalk Server environment has become corrupted.
B.
First remove the custom pipeline project from your solution then compile it separately.
Then rebuild the solution.
C.
First remove the reference to the custom pipeline from your BizTalk application project.
Then rebuild the solution.
D.
You should upgrade to Visual Studio .NET 2005 SP2.
Explanation:
By using your custom pipeline in your BizTalk application project, you create a dependency. Building these projects together creates the problem described in this scenario. Thus the best plan of action would be to keep custom pipeline projects separate to avoid such build problems.Incorrect Answers:
A: Nothing in the question remotely suggests that your BizTalk environment is corrupted. A dependency is
preventing a successful build. Thus a reinstall of BizTalk will not resolve the issue at hand.
B: The build error would be eliminated by removing the reference to the custom pipeline assembly because it would be removing the dependency that was preventing the build from occurring. However, the consequence of this action would be that your BizTalk application assembly can no longer make use of your custom pipeline assembly.
D: While it is always recommended to work with up-to-date development tools; but the issue at hand has nothing to do with the service pack in use with Visual Studio. Furthermore, upgrading will not solve the problem.