Bug when changing from VSS to SVNSCCproxy

( SVNSCC , VS 6.0, 1.2.1_050822, WIN 2000/XP )

Type: Public Status:Closed Created: 07 Oct 05 10:00 Updated: 18 Oct 05 10:00

--> Igor Pushkov (admin) at 18 Oct 05 10:00 writes

After importing sources to Subversion you have to delete local folder
completely and then pull it back again with Tortoise. Then you should call
«Change source control» and confirm the bindings. That's all.
You either need to add all sources to svn rep through the IDE (deleting the
old bindings to source control) either follow the instructions of chapter
«How to bind to project which is already in SVN»
(http://www.pushok.com/help/svnscc/index.php?redirect=adv_openalready.htm).

--> pi-consult gmbh Hilgarth (user) at 12 Oct 05 10:00 writes

Hello,

I did the following:
- Open project in IDE with VSS as provider.
- "Get latest version"
- Close the IDE
- Import the project-folder in my SVN-repository using TortoiseSVN
(right-click on folder -> Import).
- I switch the scc-provider to your plug-in. I open the project in the IDE.
I specify the path to my repository and select the module. When clicking on
ok, your plug-in creates the .svn-folder for the project-folder but not for
any sub-folders.

Kind regards,
Daniel Hilgarth
pi-consult gmbh

--> Igor Pushkov (admin) at 10 Oct 05 10:00 writes

How you understand the switching? Usually this means that you:
1. Convert your existing source safe database to new format.

2. Open project/solution from new database. Or pull it somehow from server
and then bind project to new source control.

It is not possible to change source control just opening it from the same
location just with new provider (our plug-in).

--> pi-consult gmbh Hilgarth (user) at 07 Oct 05 10:00 writes

Hello PushOk-team,

Let's assume, I have a project, which was in Visual Source Safe. I got
the latest version, all files are read-only. The project has a
subdirectory, in which the resource-files are stored. Now I switch to SVN
SCC proxy and open the project in the IDE. It asks me for the SVN URL and
module. I specify those and hit ok. SVN SCC proxy now creates a
.svn-directory and everything is fine, except one: It does NOT create a
.svn-directory for my subdirectory, so the files in this directory are not
under source-control.

I use version 1.2.1_050822

Kind regards,
Daniel Hilgarth
pi-consult gmbh

Rate this ticket:

Not useful at all

Partially useful

Useful

Very useful

Ticket

Bug when changing from VSS to SVNSCCproxy