dotSoftwaredotDevelopmentdotCustomersdotAbout us
PushOk logoblank
bullet Home
bullet My software
bullet Support
bullet My payments
bullet My info
bullet Subscriptions
bullet Voting
bullet Contact us
fast linksFast Links
news&eventsnews and events

2012-12-21 
Major update of SVNCOM version 1.7.2 are finaly released

2012-12-21 
Major update of SVN SCC plug-in - versions 1.7.2 are finaly released

Lightweight embedded Node.js database with MongoDB API.

Ticket

Search go
PushOk Logo blank
leftTicketright

cannot add web project to source control

( SVNSCC , VS .NET, Latest, WIN 2000/XP  )
Type: Public Status:Closed Created: 04 Jan 05 01:00 Updated: 02 Feb 06 02:00
--> Igor Pushkov (admin)  at 02 Feb 06 02:00 writes

The issue should be fixed in plug-in 1.3
--> brett (user)  at 04 Jan 05 01:00 writes

Here's an informative update on my problem:

If, from my local computer, I create a single empty solution under the
wwwroot of my web server and then try to add it to source control, it will
fail with the message that the path "is not a working copy". However, if I
go to "map network drive" in Windows Explorer and map the web server's
wwwroot to my computer as, say, my "W:" drive, I can then add it to source
control no problem. Apparantly there is a problem with how the file shares
are accessed. When the web server's wwwroot is not mapped to my local
computer, the Local Path in the "add solution to source control" dialog is
listed as "\\theserver\Inetpub\wwwroot\testsolution" and I get the
following error:

"svn: '\theserver\Inetpub\wwwroot\testsolution' is not a working copy"

but if I map "\\theserver\Inetpub\wwwroot\" to my local computer as my W
drive, when I go to add the solution to source control, the Local Path is
now listed as "W:\testsolution" and everything works fine. This wouldn't
be a problem except for the fact that when I'm setting up *web projects*
they always use the full share name... and there is no way for me to change
the Local Path field in the "add solution to source control" dialog because
it is greyed out. So web projects cannot used a mapped drive for the Local
Path and I keep getting this "not a working copy" error when I try to check
them in. Help!
--> brett (user)  at 04 Jan 05 01:00 writes

I am attempting to add a solution containing a web project to source
control. To keep things simple, I will walk through a step by step example
of how I am attempting to do this. First, I create an svn repository on my
Linux source control server (I access this using the svnserve server).
Next, from my local machine, I create a new blank solution and then add a
new web project under it. I have VS.NET create the solution on my Windows
2003 web server and organize the web project under that in order to stick
to the prefered directory structure. I now run into a problem when I go to
add the solution to source control. The solution itself is added fine... I
log into my svn server and create a module for the solution. I cannot
change the "local directory" (it is greyed-out) but it is properly set to
the correct directory on my web server. I am the prompted to add the
project to source control. I follow all of the same steps as before, but
when I click ok, it fails and gives me a message that the local path is not
a working copy. This refers to the file share path on my web server that
contains the web project. I noticed there was a previous ticket created
about this problem (titled, "svn: "\mrdata2.xyz.com\wwwroot$\CASDB" is not
a working copy"), however, the solution given for that ticket just says to
use file share instead of Frontpage extentions. I AM using file share
though and I still get this error message. Any ideas?
Rate this ticket:
Not useful at all
Partially useful
Useful
Very useful



You are 9755008 visitor since 20 Jan 2003.
1091 visitors today and 4 online right now.
blank left to top right blank

© Copyright by PushOk Software, 2003-2024, webmaster@pushok.com