How Long Germs On Chapstick

Hello

a few years ago I use the VSS (Visual SourceSafe) to administer programs and no single source of VB but also other languages \u200b\u200blike Clipper and C, the interesting thing about this tool is that it allows multiple people working on a software project so that each one has a local copy of the software (or part thereof) so that you can build, change, delete or add programs and new resources. The local copies are disposable because the sources are stored in a database managed by the VSS Below we describe the basic functions and how to start using the assumption that what we will do maintain the source of a project from VS 2005.

1. After installing the VSS which is in the VS 2005 Team Edition, will be created 2 shortcuts to VSS is an "Administration Visual SourceSafe "and the other is" Microsoft Visual SourceSafe. " The first allows you to create databases, users, permissions and publishing via the Web, the second serves to work with files stored on the projects they are stored in the VSS database.
2. first thing to do is create a new database, give it a name ubicacióny. This is done from the administrator of the VSS by a very clear and easy wizard. Then users should be created, preferably with the domain user name, that this is justified when we see the web access (in a future post) With the BD
3. created and get into the VS and open the application you want to store in VSS. In Solution Explorer, right click on the solucióny select the "Add Project to Source Control", began an assistant with the following steps:
   1. Ask & # 225; the VSS user will create and design and database to which you want to add the project and which is registered in the user name.
   2. If the user and the database exist, a dialog box asking a name for the root project suggesting something like "MiSolucion.root" I prefer to delete that name and leave the box blank, one field is the ubicacióny appear with the value "$" which indicates the Following the BD, I prefer to leave it unchanged, After this operation, the solution will be stored in the database

r

After the solution stored in the database will have the VSS source control and will appear in the VS project with a new property next to each file will see a padlock, which means that the file is saved in the database and available for modification, in the jargon this is known as VSS "protected file."

Now the right click on any file in the Solution Explorer displays the following menu

previous menu options are for the following:

"Out for Edit" enables the file so it can be editable and you mark it in the database, so that no other user can modify the duration of our Edition. This is true if the database was created with the model "Lock-Modify-Unlock" which does not allow competition in the amendments, there is another model that is "Copy-Modify-Merge" which allows concurrence in the amendments and that was the only model supported by the previous version of VSS. To "check out" (check out) the file goes from ReadOnly to ReadAndWrite

"Get Latest Version" Bring the database the latest version the selected file.

"Compare" to compare the version of the file is on your machine against the one stored in the database and displays the differences in case they exist.

"View History" to view the file change history, who made them when and what were the changes made, plus the ability to compare versions or compare a version with the local copy. Well

this as an introduction to the VSS think that may be useful

Salu2

Sergio

Oil Of Oregano Vs Colloidal Silver

managing Visual SourceSafe VS2003 and SQL Server 2005

Hello

After a good holiday back to write here this time going back in time with VS 2003, I tell my case, I have VS2003 and VS2005 systems and SQL 2005 and SQL 2000 and as I have only one development machine so there I have the VS 2003, VS2005 and indeed is there no problem, also I have the SQL Server Express 2005 and I restored a database sql 2000, the truth without any problems I started working with these 3 tools, that was true until I tried to create classes DataAdapters components through VS 2003, it was impossible not generate SPs the solution to this issue was very easy and the comment, have only to install the SP1 of VS 2003 and ready. About

Use SQL2005 to handle BD that were created with the SQL2000 I have a few comments that I put here:

1. restore the database from a backup data, not previously create the SQL2005, ie direct vayqn restore, do not try to create first and restore later.
   
2. Keep in mind that they can no longer restore a SQL2005 backup made in the sql 2000, at least I found how to do it.

Well this was a short delivery and without code but I think very useful for those who no longer want to use the SQL2000 and SQL2005 to jump into, at least in their development machine

Salu2

Sergio