What version of Ankh should i choose for Visual Studio 2010 and TortoiseSVN 1.6.7, Build 18415 - 64 Bit
Thanks.
Use the newest version of AnkhSVN, that would be Version 2.1 at the moment.
AnkhSVN is a standalone subversion client that is completely independent of TortoiseSVN.
If you are looking for a Visual Studio add-in, that is using TortoiseSVN, use VSTortoise:
https://vstortoise.codeplex.com/
AnkhSVN 2.3.11269 (and maybe other versions) is "dependent" on TortoiseSVN (=Subversion client) / working copy format version.
Just got this message after installing/using AnkhSVN 2.3.11269:
Subversion detected a working copy that needs an explicit upgrade in '...'.
While this working copy is not upgraded all files in this working copy will appear as new.
When a working copy is upgraded it can no longer used by Subversion clients that weren't designed for this (or later) working copy formats.
So I gave VsTortoise a try since it still supports Subversion 1.6 --> VsTortoise is a "normal" VS plug-in not a "SCC provider". It just adds TortoiseSVN commands to VS. TortoiseSVN seems to be mandatory anyway! It is just a lightway alternative to AnkhSVN but does not support e.g. moving files on the client/working copy.
Related
Hi I made the mistake of experimenting with an Apple Mac just before the lockdown and now im stuck with it. Now I am trying to work on a tfs project in os as both bootcamp and parallels drivers drain the battery too fast.
As TFS is not supported in visual studio for Mac I have been trying to get it to work in visual studio code. I have installed the extension, but can't get tee clc working (I think its no longer supported)
It appears that tee clc is not compatible with the latest version of oracle.
I have tried installing oracle 10 and folowing this fix here but I get an error java.lang.module.FindException: Module java.xml.bind not found
can anybody point me in the right direction. I feel like im missing something as this should not be so hard.
Is TEE clc the right tool to be using. If not how should this be done now?
Thanks
We do not have TFS source control, assume you are talking TFVC source control. You are right, it is not support with Visual Studio Mac right now. But if you are using Git, it's available in Visual Studio Mac.
More details please take a look at our official doc here-- Does Visual Studio for Mac support Team Foundation Version Control?
Unsupported workarounds for TFVC
While Visual Studio for Mac doesn't officially support TFVC, the rest
of this guide provides some workarounds to work with TFVC on macOS. If
you're using TFVC for version control today, here are some solutions
you can use to access your source code hosted in TFVC:
Option 1. Use Visual Studio Code and the Azure Repos extension, for a graphical UI
Option 2. Connect to your repo using the Team Explorer Everywhere Command Line Client (TEE-CLC)
So, Tee clc is the right tool to be using.
tee-clc (can be installed with HomeBrew), which depends on Java 6, 7,
or 8 (see How to install Java 8 on Mac -- as of this writing, Java 9
will not work.)
Make sure you have installed java 8 on your Mac machine. You could also take a look at replies in this question: Connect VS code with TFS on mac It provide step by step guide of installation and configuration.
You could use https://github.com/microsoft/team-explorer-everywhere CLI tool for TFS support on Mac, or using older JetBrains IDE with TFS plugin,
for example I am using Rider 2019.3.4 with TFS plugin(already obsolete).
Screenshot of JetBrains TFS:
Trying to run an old project in Visual Studio 2015. It was created in 2012 or 2013, I cannot remember which. I have uninstalled both programs as I was running out of space, and i think that is what caused this. I get the following options:
And I do not want to change the target, so clicking on the second option brings me to https://www.microsoft.com/net/targeting which I can't seem to find anything there that remedies the situation. Is there a way around this without reinstalling the old version of Visual Studio again? Will that even fix my problem? Thank you.
Just Reinstall Visual Studio. When you uninstalled previous version it caused this problem.
You could try doing a repair reinstall of Visual Studio 2015.
Another point to consider is that Windows 7 (the oldest version of Windows still supported by Microsoft) includes a Windows Update for the .NET Framework v4.6.1 categorized as an "Important" update. I have not confirmed with Windows 8, but I suspect it, too, includes a similar update. Windows 10 comes with .NET 4.6 to start with. That means that any up-to-date supported machine today will be able to run apps targeting any .NET version up to and including 4.6. I recognize that there may be other reasons to continue targeting an older .NET version, but I bring this up just in case the concern is support on client workstations.
I installed Ankhsvn 2.3, but that assumes I'm using Subversion 1.7, which I'm not. Now I'm trying to install Ankhsvn 2.1, but it says that I'm unable to install because a newer version of the product is already installed.
So, how do I uninstall Ankhsvn 2.3? I can't find the uninstaller.
The Windows design guideliness tell application developers that they should just add uninstallers to the Start->Control Panel->Software list. So this is where you can find the AnkhSVN uninstall (like that of any other MSI)
Adding an unnecessary uninstall icon in the program menu would even be a design error for a 'Designed for Windows' application.
Running on Windows Server 2008 R2 with Windows 7 client.
I downloaded and installed VisualSVN Server 2.5.2 without a problem. The page here indicates that this is built against Subversion 1.7.2.
I downloaded and installed TortoiseSVN 1.7.3 without a problem. The page here indicates that this is built against Subversion 1.7.2.
Now I would like to install ankhsvn for use with Visual Studio 2010. The latest version is 2.3.10509 and the page here indicates that this is built against Subversion 1.7.1.
Does anyone know if this will run correctly against my SVN server? Or do I need to wait until ankhsvn release a version built agains SVN 1.7.2? If I need to wait, how promptly do ankhsvn releases usually appear?
Source control is obviously critical so I don't want to risk losing any data by "just trying it".
Subversion versioning requires clients to have the same minor version. So any 1.7.X client should be compitable with every other 1.7.Y client.
For the server, any 1.X client will work with any 1.Y client.
Of course it's a good idea to keep things as up-to-date as possible, but you're not risking anything by combining 1.7.1 and 1.7.2.
The release of AnkhSVN based on 1.7.2 will be out in the coming days, the daily builds are already using this.
From what I'm aware of, we had to upgrade SVN on our servers to be compatible with the latest version of ankhsvn. It was a big deal, for the leads let us know we couldn't use ankh until we updated.
We are also using Tortoise.
Hope that helps.
Can I use new SDK directories that comes with VS2010 for VS2005 ?
I expect you can, but unless you need that specific version the simplest thing to do would be to download the latest Windows SDK instead:
Microsoft Windows SDK for Windows 7 and .NET Framework 4
This is more recent and can (IIRC) automatically integrate into VS2005.
If there is going to be an issue with this or with the VS2010 SDK then it will be because the .lib files are incompatible, e.g. through an object file format change or through a whole-program-optimisation intermediate representation change. However most if not all of the .libs in the SDK will just be DLL headers and so this shouldn't be an issue. (In the SDK release notes there is actually a link to a supported hotfix that improves compatibility between VS2005 and VS2008 objects but it sounds like VS2005 SP1 will usually be enough.)
There's a slim chance that the header files might not work (or might assume a different set of default defines) but in general the Windows header files are very careful with defines and version testing that I doubt this would be an issue.
If you're asking if you can use ATL + MFC from the later version then I think this is less clear cut, and may require a recompile of their sources in the older compiler. In that case I think your best option might be to upgrade to VS2010 if that's possible.