Biztalk Visual Studio Interview Preparation Guide
Download PDF

Biztalk Visual Studio based Frequently Asked Questions in various Biztalk Visual Studio job interviews by interviewer. These professional questions are here to ensures that you offer a perfect answers posed to you. So get preparation for your new job hunting

26 Biztalk Visual Studio Questions and Answers:

1 :: Explain me what is strong name key?

A strong name ensures that each assembly name is unique. Each assembly in your BizTalk project requires a strong name in order to deploy successfully.

2 :: Tell us are all the BizTalk development tools embedded in Visual Studio?

No. Indeed BizTalk Mapper Editor, Schema Editor, Orchestration editor and Pipeline editor are embedded in Visual Studio. However BAM and BRE tool are not embedded.

3 :: Do you know what is Build Order and can it be changed?

Build Order is the sequence in which the projects will be build when the whole solution is build and yes it can be changed.

4 :: Please explain what are Advantages of BizTalk Server?

☛ A. It is basically an Integration server. It helps in Integrating Enterprise Applications at one common point.
☛ B. Solutions can be developed really fast with BizTalk Server. Effort spent will be less.
☛ C. Updates can be handled in an easy way and maintenance will be easy. BizTalk Server supports Versioning of Artifacts.
☛ D. Negative scenarios can be handled easily with BizTalk Server- e.g. If some Service is down, we can set Retry Mechanism,
☛ E. Alternate Transport Mechanism. It even supports service windows. We can take advantage of enlist and stop features and prevent losing even a single Message.
☛ F. BizTalk is designed to operate in Multi Server Environment. We can run the application on various servers to manage load and Availability.
☛ G. MessageBox DB designed for optimum performance.
☛ H. Advantage for customers on cost saving in terms of development time.
☛ I. BizTalk has a number of Tools like BRE, BAM, SSO which be effectively used.
☛ J. It can be used to communicate with wide range of Legacy Applications. There is always a scope to develop custom Components.

5 :: Tell us how do you achieve First-In-First-Out message processing of messages received from multiple sources using an Orchestration?

• Use a Sequential Convoy to process the messages in the order they are received into the Message Box.
• Make sure Ordered Delivery is set to True inside the Orchestration Receive Port.

6 :: Explain me in which scenarios would use a “promoted property” vs “distinguished fields”?

The rule here is, if you don’t want the schema element to appear in send port filters/debugging information then make it a distinguished field.

7 :: Tell us what purpose does Visual Studio serve?

Development for BizTalk Server is done through Visual Studio <version> (depends on BizTalk version). Visual Studio has templates for BizTalk artifacts like orchestration, pipelines, schemas and maps, so a BizTalk solution can be created (design time) and deployed to the BizTalk runtime. Besides artifacts .NET development can be done in creating pipeline components, custom functoids, custom adapters, and .NET helper classes to aid in orchestrations. As a BizTalk professional Visual Studio is your friend and required to build BizTalk solutions.

8 :: Tell us why we get the error "Unexpected error writing metadata to file <filename>"?

It is a known issue of Visual Studio. Visual Studio will not successfully compile a project if it would result in an assembly larger than 75 megabytes (Mb).

9 :: Explain me how do you call a Non-Serializable .Net helper class inside an Expression Shape?

☛ • Add a reference to that class.
☛ • Make sure your Orchestration is Long Running transactional.
☛ • Add an Atomic scope.
☛ • Create an Orchestration variable of that class inside the scope.
☛ • Create an instance on that object inside the scope.
☛ • Call the method.
☛ • Bonus: Mention the class must be strongly signed and in the GAC.

10 :: Explain when working with Schemas, Maps, Pipelines, and Orchestrations, how should the projects be structured?

☛ • Schemas and Maps in its own project
☛ • Or Schemas and Maps together in its own project
☛ • Orchestrations in its own project
☛ • Pipelines in its own project