What we're going to do is the following. On the BimlScript.com site, we will expose a webservice API and a HTML5/Silverlight app that lets you import individual dtsx files or entire projects (including multiple dtsxs, conmgrs, dtprojs, etc.) We're
doing it this way for several reasons:
1) We hear a lot of requests for making Biml-related services available programmatically. This would allow you to programmatically import whatever you need.
2) Importing entire projects or large pieces of projects is not terribly compatible with how the BIDSHelper/VS-addin model works. For those cases, we would need something that was standalone or standalone-like anyway.
3) It allows us to deploy the new functionality without having to make updates to the BIDSHelper plugin. On the next version of BIDSHelper, we'll talk with the team about how to better integrate import into the plugin - but this lets us get the capability
out to the community more quickly and without asking non-Biml users to take an update for Biml-only functionality.
4) It gives us a much easier way to service the import functionality in the short-term. While we expect import capabilities to be high-quality, we recognize that importing has many more variables than exporting/building. Packages can be exported
and modified by a variety of tools, all of which use slightly different conventions. Even something as simple as ExecutableType can be represented in up to 4 different ways for each version of SSIS. There will inevitably be some cases that we miss
early on. Hosted as a service, we can turnaround fixes in hours or days rather than weeks or months.
5) A big goal for Biml is to create a huge library of scripts across the internet to solve common problems. This will enable beginners and experts both to search for keywords and find a BimlScript that gets them 80% of the way to a solution. By
making it a service, we can also make it easier for people to share what they're importing. We will ABSOLUTELY protect privacy of everything that gets imported. But for those people who choose to share, a service-based approach cuts out multiple
Please let me know if you have any questions or concerns about that, as we still have some time to make course corrections on this approach.