Closed knoxi closed 3 years ago
@knoxi can you please share your .csproj file with us? From the outputs and the exception you received, it looks to me like you have a ProjectReference to a project whose artifact is a .dll file as opposed to a .dacpac file, which won't work.
@jmezach looking at the code, I don't think we're being defensive in validating that references are dacpacs, maybe we should use this issue as an opportunity to add that check?
@jeffrosenberg Yeah, that makes sense. I'll rename this issue to reflect that.
@jmezach just let me know if you'd like to take this or if you'd like me to, this shouldn't be much work
To be honest I'm a little bit burned out at the moment due to personal reasons so if you'd like to take this that would be much appreciated!
No problem, I'll take care of this tonight or tomorrow :-)
We have created a custom SSDT extension for advanced database scheme migrations. You can find it here: SSDT Data Migration
I used this code base to reproduce the error above, I have only modified the TestProject files referencing the SSDT extension project directly instead using the official package we published. Then I finally can see an error, otherwise I wasn't able to see something going wrong but the dacpac always had empty scripts instead merged content.
I have attached the changed project files. I also had to increase the output verbosity to see the detailed error.
Thanks for the updated release. I was able to fix my issue since I noticed that referenced project wouldn't work, I just added them for debugging purposes.
I'm getting an exception building the dacpac. It looks like it's an error while calling a library by reflection.
Any idea how to dive into this and fix or workaround it?