Without flailing through a file search, how does one track down the code that caused an error during SSDT publish preview?
Normally any errors come later such that the statement can be traced in the publish preview, but when the error comes in the preview I see no clear way to find what caused it.
Update: The faulty code was in a stored procedure already existing on the server. Even though I removed it from my database project it still failed the publish preview, so I had to delete it from the server to make the publish work. So a file search didn't even work to find the code it flagged.
Update 2: The error isn't actually failing the publish preview (at least by itself), it is just shown only when the step fails (I have since seen it appear again). The actual error is still unknown as the only other messages were data loss warnings that the advanced settings were set to allow. I am now confused more than ever.
Also related: Unaliased ORDER BY columns.
So I'm guessing this is actually a bug in SSDT at this point. Can anybody confirm? I'd still like to know how to track down the buggy code when it is on the server and fails the publish preview.