Service Bus Connect is organized in two big modules:
As we can check some components are common in Developer SDK and Runtime&Tools, this is because in a normal business environment we assume that is going to exist a machine to develop the applications and another to have them running.
With this last step the process is finished and now we are ready to use Visual Studio to create our Service Bus EAI and EDI projects.
To create a new project you just need to:
The EAI environment to work on Visual Studio project is very similar to BizTalk 2010, however some functions won't be available in Windows Azure eai and edi labs, functionalities like generating a schema instance or validating a schema, so useful in BizTalk to test our maps. My suggestion is that if you have it, use BizTalk in parallel with your eai and edi project and with this have all functionalities by your side, this because testing bridges deployed in the azure cloud can be quite complicated because errors returned by the debug console are insufficient. To insure that errors are not in our schemas or maps we should use BizTalk server. This lack of functionalities is because Azure EAI and EDI labs is still in a development stage, so I hope, this April version is much better than the first release so lets hope some other release brings us the full package. Thanks, Rui Pedro Machado I was recruited by Sandro Pereira!
Naomi N edited Revision 10. Comment: Article needs more work
Carsten Siemens edited Revision 6. Comment: fixed typos