Re: Source Safe vs. VS 2003 Integration Issues



Forget about the integration,especially if you are having this many
problems. Just go into VSS and manually check out the files you need. This
will avoid all problems, with only 5 extra seconds of work.

"Richard" <Richard@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:870916DD-71F4-4FAC-9CE7-33783A77E48C@xxxxxxxxxxxxxxxx
> Sorry about the cross posting from the VSS newsgroup but I didn't get any
> help there yesterday and I know this group is heavily traffic-ed. If I
> sound
> annoyed and ticked off it's because I was:
>
> I'm Running VSS 6.0d with VS 2003...
>
> ARRRRGGGHHH!!!
>
> Could someone POSSIBLY ATTEMPT TO EXPLAIN to me why it is that every time
> I
> try to add a solution to SS from within the Visual Studio IDE the SS tree
> is
> created with 2 {or more} extra layers of project folder hierarchy? I have
> been using integrated SS since Visual Studio 6 and I have NEVER seen this
> extremely aggravating behavior ever before!!
>
> And for bonus points could someone please tell me how to turn off the
> nearly
> equally extremely annoying ".root" that gets appended to a project name
> every
> time I am prompted to create a project? I have never seen this "feature"
> before either...
>
> Example:
>
> 1) Developer clicks "Add solution to Source Control" from IDE for project
> on
> local drive at:
>
> C:\PHN\PHN\NunitTests {code lives here}
>
> 2) Developer is prompted to create NunitTests.root project.
> 3) Developer erases extremely annoying ".root" that he did not want
> appended
> to his project's name
> 4) Developer browses SS create dialog such that project SHOULD be created
> at:
>
> $\PHN\PHN\NunitTests
>
> 5) Developer clicks Ok
> 6) Hour glass appears and Source Safe creates:
>
> $\PHN\PHN\NunitTests\NunitTests\NunitTests {versioned code lives here}
>
> 7) Developer gets extremely angry as he spends 10 minutes
> moving/renaming/deleting in SS and unbinding/binding in VS...
>
> HOW DO I DISABLE OR DESTROY THIS EXCEEDINGLY ANNOYING "FEATURE"???????
>
> --Richard
>


.



Relevant Pages

  • Source Safe vs. VS 2003 Integration Issues
    ... Sorry about the cross posting from the VSS newsgroup but I didn't get any ... Developer is prompted to create NunitTests.root project. ... Developer erases extremely annoying ".root" that he did not want appended ...
    (microsoft.public.dotnet.languages.csharp)
  • SS vs. VS 2003 Integration Issues
    ... Developer clicks "Add solution to Source Control" from IDE for project on ... Developer is prompted to create NunitTests.root project. ... Developer erases extremely annoying ".root" that he did not want appended ...
    (microsoft.public.vstudio.sourcesafe)
  • Re: SourceSafe issues continued
    ... This updates his project with what was changed by Developer A. ... Hence my belief that 'Update Project List' is one way, from VFP ... to VSS, over-writing any changes previously made to the PJM. ... > using the VSS integration. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: VSS best practice for promoting code to production?
    ... might label it in VSS, then we will move it from our dev environment ... After the testers shake it out and determine that it's production ... The developer may label it again as a production ... The SysAdmin performs a get version from the developer's VSS. ...
    (microsoft.public.vstudio.sourcesafe)
  • Re: VSS best practice for promoting code to production?
    ... might label it in VSS, then we will move it from our dev environment ... After the testers shake it out and determine that it's production ... The developer may label it again as a production ... The SysAdmin performs a get version from the developer's VSS. ...
    (microsoft.public.vstudio.sourcesafe)