I am trying to upload a solution with multiple projects but only the first project gets uploaded. When I try to load any of the others I get error "Project cannot be added to Subversion because it is out of working copy"
The folder structure on the drive is:
c:\myprojects\thisproject\project1
c:\myprojects\thisproject\project2
c:\myprojects\thisproject\project3
How do I remove a solution from the SVN library via VisualSVN? I don't see a remove solution, just add a solution.
I don't believe it's possible to remove a solution from SVN via VisualSvn. The options are either delete or export and only delete can be done, but that also removes the file from the solution and in most cases from the harddrive. VisualSvn offers minimal SVN features: update, commit, delete and branch commands.
I recommend if you are having problems with svn that you used Export from TortoiseSVN. Export removes all the .SVN folders from your solution and copies them to a new location.
If project1 is the root of your subversion repository, project2 or project3 will not add to your subversion repository.
Related
I use P4V to manage my Perforce files. One issue that is very confusing is that when I rename folders in P4V using Rename/Move, Perforce keeps the older version of the folder but with empty state. Basically the rename goes forward successfully but Perforce keeps the previous folders with no files in them.
Is there a way to get rid of the old folders after a rename or move?
thanks
In your clientspec, make sure you have rmdir in the Options line, not normdir.
Is there a way in teamcity to restore a deleted build configuration. I found Restore just deleted project which is about restoring a deleted project but can't find any information about restoring a deleted build configuration. I am using Teamcity 8.0.6
TeamCity 9, locate your data directory and you'll find a trash folder, like so:
D:\TeamCity\Data\config\_trash
Take a copy of the whole thing to some other folder, just in case.
Move the effected project folders from config\_trash to config\projects.
Remove the suffixed .projectNN from each project folder.
You may see critical errors in the main web portal while this is happening.
Restart TeamCity just for good measure.
The previous versions of build configuration setting are stored in /config/projects/buildTypes folder in different *.xml.N files. To restore setting replace *.xml file with *.xml.N file.
Also since TeamCity 9 it is possible to store all project setting in VCS.
Another option, available since 9.0 is to place project settings in version control (Git, Mercurial, or Subversion and Perforce since 9.1), and then restore removed files using VCS commands.
I have a project in VS2010 and that project exists in SVN through AnkhSVN.
I want to create a project with the same code as the existing project. I don't want to branch. Has to be a completely different project, but I want to start with the existing files from an existing project. I do not want the name from the current project listed anywhere in the existing project.
How do I do this?
Thanks for your help.
There is no specific operation in SVN as branching, all operations (tagging, branching) are just essentially making copies within SVN repository (however on SVN server these are not separate copies, i.e. you are not doubling space on server side, but instead the cost is almost nothing). So, all you need is just copy it to another location and start working there:
$ svn copy svn://host.example.com/repos/project/trunk \
svn://host.example.com/repos/new_project/trunk \
-m "Creating a new_project based on project"
After that, you probably would want to switch local working copy to point to the new_project location on the repository:
$ svn svn switch svn://host.example.com/repos/new_project/trunk .
My team created a project. This project has already existed on each PC of each member. Now, I have just added this project to SVN using AnkhSVN. So I want to know how to each memeber of my team can use this project without check out or download this project because it has already existed. I want to using any SVN client to refer to it or something like that. Any idea for me ?
Short answer: they have to use SVN checkout into empty folders, sorry.
Ask your team members to:
create new folder named "fromsvn",
make an SVN checkout of project into that folder,
copy with replace existing project into "fromsvn" folder,
commit changes if there are any.
Long answer:
During checkout SVN creates folder named ".svn" in each folder. This ".svn" folder contains the so-called "base" versions of your files. Each "base" version is a copy of the original file which is inside SVN.
When you make "clean" checkout (i.e. you download project from server into empty folder using SVN client), SVN creates both "base" versions of files (and puts them into .svn folder) and "working copy" - the ones you actually will modify and then commit. Thus, if you checkout 10Mbytes project, SVN will create 20Mbytes of files, half of which will be stored in ".svn" folder, but it will download only 10Mbytes from server.
Other members already have their projects, but they do not have ".svn" folders. It means, that SVN client still have to download those folders from SVN server repository, and it will still cost those 10Mbytes.
I started to work on a project without setting it up for SVN .I am using Visual studio 2008 and AnkhSVN. Now I have new copy of code on my local and SVN has older copy.How should I checkout those files and commit them?
Thanks
The easiest is probably with the command line client (or TortoiseSvn with similar options). You're looking to do a checkout with the force flag on:
svn co --force <URL> <WC>
From the help:
If --force is used, unversioned obstructing paths in the working
copy destination do not automatically cause the check out to fail.
If the obstructing path is the same type (file or directory) as the
corresponding path in the repository it becomes versioned but its
contents are left 'as-is' in the working copy. This means that an
obstructing directory's unversioned children may also obstruct and
become versioned. For files, any content differences between the
obstruction and the repository are treated like a local modification
to the working copy. All properties from the repository are applied
to the obstructing path.