I had no sooner published my blog post about the coolness of Biml 2018 when I encountered a bug trying to use one of the features I really like – converting SSIS packages to Biml using (FREE!) BimlExpress 2018 with Visual Studio 2017.
My first response was, “Durnit! This worked in the test versions.” My second response was to drop a note into an issue-tracking site Varigence set up to record these kinds of things.
And then I started getting emails similar to, “Hey Andy, I get this error when I try to use the new ‘Convert SSIS Packages to Biml’ feature”…
David Stein to the Rescue!
David Stein (blog | @Made2Mentor) dropped a note onto the BimlHero Support channel about this issue, along with a workaround: If you add a Biml file first, and then try importing SSIS packages, it works. You don’t even have to save the Biml file. Simply create a new Biml file. That’s enough. You can delete it. After that the “Convert SSIS Package to Biml” functionality works (click to enlarge):
Varigence is aware of the issue and is working to address it. Be patient.