Issue #1: I find this happens most when I have two instances of VS.NET open
at the same time. The last one closed overwrites the other.
Issue #2: ASP.NET? Fairly typical, as you have to refresh the project to be
up to date with SourceSafe. It is unfortunate, but predictable, and is more
due to the nature of web development than a bug in SourceSafe or Visual
Studio .NET. If you are having the same issue with web forms and the like,
you may have discovered a bug.

Signature
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
**********************************************************************
Think Outside the Box!
**********************************************************************
> Something doesn't click here --
>
[quoted text clipped - 12 lines]
> Thanks,
> -roko
roko - 17 Feb 2004 19:41 GMT
1. I can see why the project list wouldn't save because of two or more
instances of VS.NET running.
2. Hmm, so at the sln (solution) level, no changes are made so that would
make sense.... I guess I would have to add to the wish list that we may
optionally set the Modified column to reflect modifications done WITHIN the
project rather than a "superficial" solution file.
Cowboy Up!
"Cowboy (Gregory A. Beamer)" <NoSpamMgbworld@comcast.netNoSpamM> wrote in
message news:eYdmzbX9DHA.400@tk2msftngp13.phx.gbl...
> Issue #1: I find this happens most when I have two instances of VS.NET open
> at the same time. The last one closed overwrites the other.
[quoted text clipped - 23 lines]
> > Thanks,
> > -roko