Recent content by microcog

If you add the solution to source control, all files that need to be added to source control are added automatically.

It should be very easy to get source control integration in Visual Studio .NET. Steps: 1. Install VS.NET Professional, VS.NET Enterprise Developer or VS.NET Enterprise Architect. 2. Install VSS. If you purchased Visual Studio .NET Professional, you'll have to purchase VSS standalone as well...

Visual SourceSafe supports shared, or multiple checkouts. Exclusive checkout mode is enabled by default though. To switch a database to shared checkout mode: 1)Open your database in VSS Administrator, 2)Click Tools|Options and on the General tab, select "Allow Multiple Checkouts&quot...

shaneras, When working from the command line, there are three environment variables that are important. You got the first two, PATH and SSDir. For some in depth information about these variables, see http://blogs.gotdotnet.com/korbyp/PermaLink.aspx/9a1cd38d-d101-41d8-997a-ccd02c2661e6. The...

Are you sure that you ran Analyze all the way through? I've heard that if you interrupt the utility midrun, bad stuff can happen.

Hi, To get VSS, you have to buy the Enterprise edition. IMO, the extra cost is well worth it. On top of what you get in VS Pro, the Enterprise edition has MSDE (the no-UI version of SQL Server with a limited # of licenses), which is really nice if you'd like to dabble in database development...

Hi, There should be an um.dat in your data folder... Um.dat stores database users. Unfortunately, it also stores a unique identifier for the database which means that you can't just copy and paste the Um.dat file from your existing database into the new one. Try to create a new um.dat file for...

Hi Gina, On your user's machine, create/change the Windows user environment variable from SSUSER=admin to SSUSER=loginID, where loginID is the user's network alias. For more extensive details, see this recent blog post, Avoiding the VSS Login Prompt at...