Share via


Goodbye dbp...Hello dbproj!

In Visual Studio 2010, Database Edition or DBPro Projects (.dbproj) have replaced the old Database Projects (.dbp) from previous versions of Visual Studio. Database Projects (.dbproj) are available in Professional, Premium, and Ultimate versions of Visual Studio.

For those who have used the old .dbp projects and have these in their solutions your .dbp projects will be upgraded to .dbproj projects when you upgrade the solution to 2010. If you need help getting started working with the .dbproj project you can find the root node of the product documentation here on MSDN.

Additionally, Deborah Kurata, a Visual Basic MVP, has recently posted a series that provides a gentle introduction into the Offline Database Project environment. You can check them out below.

· Requiem to the VS 2003/2005/2008 Database Project

· VS 2010 Database Project: An Introduction

· VS 2010 Database Project: Using an Existing Database

· VS 2010 Database Project: Adding Tables

· VS 2010 Database Project: Building and Deployment

· VS 2010 Database Project: Adding Stored Procedures

Comments

  • Anonymous
    May 12, 2010
    The comment has been removed
  • Anonymous
    May 26, 2010
    I agree with the dextro, this format does not even support building the SP's generated by the previous version.major headache.
  • Anonymous
    June 09, 2010
    The new functionality is fine, but why couldn't it just be added to existing, not replacing everything.The old DBP project where good for exactly what they did. A easy to use platform for testing triggers, sp and the like.How do you put the DBP project type into VS2010?
  • Anonymous
    August 31, 2010
    The comment has been removed
  • Anonymous
    March 28, 2011
    I agree with the dextro.We also have projects that works against a massive databaseThe .dbproj project is unusable on our database.The .dbp projects did just fine.
  • Anonymous
    October 17, 2011
    just wanted to add my 5cents.. yes bring back database projects (.dbp)! PLEASE! it worked just fine.. not sure what / whose "marketing" decision was to remove them..