I just started with VisualSVN and got things messed up. I get complaints about working copies being too old (1.6). I have 1.7 TortoiseSVN and VisualSVN 2.5.5 and have tried many things but nothing helps.
So, I just want to start over, but the option "Add Solution to Subversion" is disabled in Visual Studio 2010. I tried deleting the repository in VisualSVN Server Manager, and uninstalled/re-installed VisualSVN. But the option remains disabled.
What can I do to just start over?
There was a major change in the way metadata is organized between 1.6 and 1.7, on the client side only. So 1.6 and 1.7 can talk to the same repositories, but the can not use the same working copies.
By the sounds of it, your problem with the error message would be sorted out by pulling the working copies again using your 1.7 tools. However, I'm not sure the interop with VS will, so you could also go back to a 1.6 client install. You'll certainly want to make sure that all clients on your system are 1.6 or 1.7, not a mix.
It's really strange you have an issue with that. You can simply upgrade your working copy either through Visual Studio | VisualSVN | Upgrade Working Copy (if you use VisualSVN) or through TortoiseSVN.
Please note that the question is completely irrelevant to the server side and is only about upgrading working copy format.
BTW you can always checkout a fresh working copy.
Related
Me - Front End web developer with an ok working knowledge of writing VB.NET code but I have never built a .NET project from scratch using Visual Studio.
External developer - Experienced VB.NET developer but completely new to version control and TFS. Also extremely cheap and prone to infuriatingly poor programming practices. He does things that make you bang your head on the table.
Background
Our external developer has coded our site but over the last few years I have been tweaking aspects of pages and have managed to learn quite a bit of VB.NET along the way. He has never used source control and I don't think he's ever had to work with another developer before.
Up until now he has maintained a local copy of the website. He makes changes to this local copy and when he wants us to test it he uploads the relevant files to our dev server. I have no experience of Visual Studio projects/solutions so if I have made tweaks to things I have edited the aspx/asxh/config files in my preferred editor and then uploaded them to the dev server. If everything works correctly I ask him to download them from the server so he can update his local copy.
I have been maintaining a local git repository of the website for the last 2 years. If he makes a change I check it in.
Obviously this is a nightmare to work with so we have now insisted that he starts using version control. I recommended GIT but he has decided to use TFS.
He has now put his solution and all the files into TFS. I have installed Visual Studio 2015 and successfully connected to TFS. I have mapped the files from source control to my own workspace but I am now at a loss as to what to do next.
Questions
As soon as I open the .sln file he has uploaded it says I have checked out the file and made changes. When I check the diff it seems to be because I am using a newer version of Visual Studio than he is. Does the .sln file need to be in version control? Or are we suppose to maintain our own versions of the .sln file and simply check in everything else?
If I try and build the project it fails because the web.config is set up for his machine and not mine. How can we maintain 3 versions of the web.config file? One for my local, one for his, and one for our dev/live environments?
I am not convinced he will have added the project to TFS correctly because he's never used it before. This is basically the blind leading the blind.
Question 1:
You need to put the .sln file in version control. Before check out the .sln file, please do a "get latest" step, which will make sure both of you are working on the latest version. When you try to check your local version in the server, and he had uploaded his local version in the server. You may have to solve conflicts before the check in.
Question 2:
You should build your project and published the website on the server. The build agent will only maintain one version of the web.config file. If he has built the project with his web.config. And you want to build the project again with your web.config, the build agent will delete the previous web.config and pull down your version. Then build the project with your's web.config.
Moreover, if both of you are not similar with TFS. Suggest you taking a look at below MSDN link which related to source control and build.
Use Team Foundation Version Control
TFS Vnext Build
I have a team of 3 developers and I want that we should be able to work on the project from our own homes, at any time (or at the same time) and make changes to the project. Till now, we have to mail each other all the updates versions to keep in sync. We are developing the project in Visual Studio 2010 currently and use SQL Express 2008. I searched internet and got some idea about Team Foundation Server but it requires Windows Server. I don't want to get into this mess and I have a Win7 Pc. Please suggest me some easy solutions.
There are any number of low-cost (often free to open source projects) hosted source control providers out there.
Personally I use Subversion along with the AnkhSVN plugin for Visual Studio.
Mercurial and Git are also quite popular and supported within Visual Studio via plugins.
Any of those options can be setup in a few minutes (if you use a hosted solution) and will all work for a small team.
Version Control is what your looking for,and your right there are some complicated solutions out there. TortoiseSVN isn't too complicated but works well.
So I've been using VS2008 & vs2010 with the starteam 2009 integrations for a while.
in a recent updating frenzy, our IT departemnt required us to remove a bunch of "old java stuff" that
their scan tool said neede to be updated, but which java didn't update. Basically all the "for boreland" entrys.
Needless to say this killed starteam and it's integrations. Reinstalling starteam fixed it, but even after uninstalling vs2008, vs2010 starteam 9 and the integrations and reinstalling, I'm still getting this error when loading a project in etiher vs2008 or vs2010.
The project .csproj appears to be under source control, but the associated source control plug-in is not installed on this computer. Source control will be disabled for this project.
I also tried copying the java folder in borland from a working box... this fixed some folks, but not me.
Anyone know how to fix this so I can get my integrations working?
My best guess is there is some prerequsite that is not getting installed by the installers,
either becuase it's improperly uninstalled, or I'm supposed to install it manually.
So if you know what the prerequsites are that'd be a big help.
Thanks,
Eric-
Wound up reimaging the box to fix this issue, wasn't able to find the real fix.
Eric-
I hope this questions isn't too obvious or vague but I am problems searching for an answer as I'm not sure of terminology.
I am using TortoiseSVN with Unfuddle and Visual Studio 2010.
Previously I used Sourcegear's Fortress which worked really well for me but my new company uses SVN.
The problem I am currently having is:
If I edit a file in visual studio, then commit (Check in) the changes back to SVN and then
My colleague then goes to edit the same file (checks it out) from his visual studio it doesn't automatically update to the new version that I just checked in, so when he then goes to check in the file after he's changed it it throws a conflict error.
So my question is:
Is there a setting that will automatically make it update to the latest version when you check out a file? Or am I using it wrong?
Thanks for any help.
Bex
You don't "check out" files, you should update before editing. Subversion uses a different versioning model than what you're used to.
Also make sure to use a good conflict editor when conflicts do occur. Personally I use DiffMerge configured as both diff and merge tool in AnkhSVN.
After installing TortoiseSVN 1.6.0, all files loaded into an AnkhSVN enabled Visual Studio 2008 project are marked as new (blue +).
I have tried re-installing AnkhSVN 2.0.6347 and checkout the repository into a new "clean" folder. However neither seem to resolve the problem.
My question is kind of two fold, is there a resolution to this issue and if there is an in-compatibility between the two products (i.e. different SVN bindings?) is there a way to tell which combination of AnkhSVN and TortoiseSVN are going to play nice with each other.
I noticed this too a couple of days ago. This happened because Tortoise converted your working copy to 1.6 version and Ankh doesn't know how to read it.
The solution is simple: I installed the latest daily build of Ankh (http://ankhsvn.open.collab.net/daily/) and now everything works like a charm.
I can verify that this works, too.
One thing that I ran into was that I uninstalled the older version before installing the new daily build version (I installed AnkhSvn-Daily-2.1.6649.29.msi), but once I installed the new version I didn't have any source code control integration whatsoever in Visual Studio 2008!
As it turned out, when you uninstall AnkhSVN your source code control provider gets set to "None", and you have to go to "Tools | Options | Source Control" and set it back to AnkhSVN.
Once you do that, you're good to go with Visual Studio integration and TortoiseSVN 1.6.
Sadly this solution does not work for anyone using VS2003 since there is no daily build (SVN 1.6) for the 1.x branch of AnkhSVN.
The AnkhSVN team has stated that they are too busy right now to update AnkhSVN 1.x (ie the VS2002/VS2003 version), so it looks like unless someone is willing to help them with it (it’s open-source), there may not be an SVN1.6 version for VS2003 for a while.