I'm focusing on an ASP.Internet web application, we're a little team (4 students) and that we do not need a devoted server to host the database instance. So with this web application we made the decision simply to place the database file within the Application_Data folder.

However , our project is source controled on TFS, so any time you open the answer and then try to launch the net application, we obtain an expcetion stating that database is read-only. That's logical since the databse file isn't instantly checked-out.

It is possible to workaround to prevent a manual check-from the database file each time we open the answer ?


Never sign in MDF files. You need to develop any project having a deployment script that produces the tables along with other database objects you'll need. Never customize the MDF from Versus Server Explorer. Make use of a version based approach to database schema.

I understand you'll say 'but is hard', but believe me, the choice which Versus magicians show you is way worse. Not just from the team development perspective, but from deployment perspective too. Once you deploy v1 individuals site, your family will enjoy changes and wish to deploy v1.1 or v2. Every time, you'll face exactly the same dilemma: you've 4 MDF files, one on each team member enlistment, and 1 around the used site, and there's virtually no method to align the schemas. You'll finish up requesting SQL diff tools like SQL Compare, however they cost you a tonne of moneys and they are not even close to perfect if this involves maintaining a SQL schema.

Besides, getting scripts as the database source will even align well with the other source control treats, like searching for who transformed what so when.

If you can to set up "Visual Studio Team System Database Edition" add-on for Visual Studio (formerly known as "Visual Studio Team Edition for Database Professionals", formerly known as "DBPro") you are able to import your present database right into a Visual Studio Database project, which may be a part of your general Versus Solution.

This then enables you to definitely manage schema objects (tables, saved procs, permissions etc.) in Visual Studio and combines your database schema nicely with TFS.

Additionally, it enables you to definitely deploy the schema inside your Versus Project towards the database server, instantly handling modifications without leading to loss of data (or failing if data could be lost).

The add-on for Versus 2008 is situated at: http://www.microsoft.com/downloads/details.aspx?FamilyID=bb3ad767-5f69-4db9-b1c9-8f55759846ed&displaylang=en