Allow three part naming for referring a DB object in same database project
Many developers have a preference to consistently use database qualified object naming. Currently using three part naming [databasename].[schemaname].[objectname] for referring an object in same DB project results in a error/warning in Visual Studio. This is is allowed in SQL server, so it makes sense for add functionality in Visual Studio to have an implicit reference to the same database project and not generate any errors/warning in such situations.
Thanks for taking the time to share this suggestion. This item has been around for a couple of versions of Visual Studio and we haven’t acted on it. Looking at the VS “15” plans, we’re not going to take action on this item, so we’re going to close it. If the suggestion is still relevant, please either take a look to see if there’s another suggestion that’s similar that you can vote on, or open a new suggestion.
- The Visual Studio Team
not much help is it
Mark Iannucci commented
What's wrong with using [$(DatabaseName)]?