>
>Thanks Microsoft. This is even worse than Vista (I used to defend Vista).

William,

I feel your pain.

It is really too bad how the bleeding edge has been steadily moving from Beta to Community Preview to Release Candidate to First Version Release. This particular VSS problem with a mission critical piece, however, is simply inexcusable. The only workarounds we have here are to a) not use VSS (unacceptable) or b) revert back to VS2005 (too bad but not the end of the world).

Personally, I've given up on jumping into any new software or update that doesn't have "significant decimals" (e.g., x.1 or x.2 or x.3, etc.) So, for example, since MS changed the upcoming SilverLight update version number from 1.1 to 2.0, I'm not touching it until the next "significant decimal" round.

Of course, this is not just MS problem, it is a problem with increasing complexity all around us. Heck, I wouldn't use a "zero decimal" release of my OWN software <g>