Sasha Sydoruk

Just found that out recently. I had to purchase a subscription for my wife and couldn’t help but notice how nice the site looked. The workflow is very well designed and is joy to use. Opened up the source and - “say hello to my little friend” - __VIEWSTATE.

Also found this white paper on surverymonkey.com from Microsoft - Customer Solution Case Study.

http://dotnetblogengine.net - is a great starter kit from Microsoft. It is a full featured blog engine written in ASP.NET.

It is very interesting to see how things are implemented. Xml based membership and role providers. Http modules for compression and url rewriting. Cool stuff.

Someone please defend Visual SourceSafe.

This is pretty funny. I have never really liked VSS myself. There is always something better out there. Some people are afraid of the cost, but with SVN the cost is not a problem. But SVN in general is quite foreign to a Windows developer, so that’s why some people go with Source Vault. I have used it a bit and I really like it. There is some cost to it but not too much.

But to answer the questions - “Let’s assume you’re in a situation where it would impractical or impossible to quickly switch to something better, what do you do to make using VSS more tolerable?” - I guess, I would make sure that there is only one person in charge of the merging. Use a lot of branching, stick with check in/out model, check your database for integrity from time to time, and no users spread around the world hitting the same database.

And of course - backup, backup and backup.

My blog is back online. The last WordPress updated somewhat destroyed my installation and it took me a while to make things right. Anyways, I am back now.

Stay tuned for more info.