November 3, 2020 at 12:39 pm
I have a database solution in Visual Studio Enterprise 2019 which consists of four database projects. My databases live on a shared SQL Server instance that hosts multiple solutions. My database projects take advantage of objects on that instance in another database that I do not control, and is not managed in a VS solution or project.
Of course I'm getting a ton of unresolved reference errors when I attempt to build my solution because I call tables and functions in that database. How can I construct a reference to that common, unmanaged database and resolve these errors?
November 3, 2020 at 12:51 pm
Well. I found out how to generate a .DACPAC file from that unmanaged database. So I attempted to create one and, you guessed it, I got a ton of unresolved reference errors in THAT database, so the .DACPAC would not compile.
Looks like I need to have a talk with the database owners.
November 5, 2020 at 9:53 am
When adding the reference to the non-managed database, you should set "Suppress Reference Warnings" to True. I think that will get around your problem.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy