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 (6)

  1. dextro says:

    This is REALLY unfortunate. Any chance of bringing back the old database projects?   You just made my life harder.

    I have projects that work against a massive database.  I don’t want to import and manage every aspect of the database from this app.  I just want to manage the stored procs and tables used by this application.  

    Problem 2 is probably related to the first one.  I get the error: "This statement is not recognized in this context" for every stored proc in the project.  No line number of what the offending line is.  Just lots and lots of errors, even when ‘Build’ is turned off in the Solution’s Configuration manager.  For now, I’m going to have to just keep my stored procs in a ‘Class Library’ and copy and paste from there to SQL Management Studio to do my work.  

    PLEASE, PLEASE give us the old database project back.  It was just the light weight project we needed.

  2. Anonymous says:

    I agree with the dextro, this format does not even support building the SP's generated by the previous version.

    major headache.

  3. Anonymous says:

    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?

  4. Anonymous says:

    dextro, try double clicking the error.. it should take you directly to the line where it occurred in the object which it references.

  5. Anonymous says:

    I agree with the dextro.

    We also have projects that works against a massive database

    The .dbproj project is unusable on our database.

    The .dbp projects did just fine.

  6. Anonymous says:

    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..

Skip to main content