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.
Related
I have an application that I am working on. It's the Master Branch. Now I would like to continue fixing bugs with that but at the same time work on the next version.
On my front-end I am using Visual Studio Community on the Mac OS.
Can someone explain to me how I can start on another version and work on that and then sometimes switch between versions to maintain the current app?
I brought up a new VS2017 dev environment at work yesterday, which means I got the recently released version 15.3. I'm getting an internal compiler error on a VC++ project that nobody else in the organization is getting; everyone else is still on 15.2. To test my theory that the 15.3 update may have broken something, I want to install VS2017 15.2 (or even 15.1 or 15.0). But I can't figure out how to do that. When I run the 15.0 or 15.1 bootstrapper, it still tries to install 15.3.
I've already gone over this guide for creating offline installations but it doesn't say anything about getting an older release. I found a guide here that shows how to use a specific release with VS2015, but I can't find anything for VS2017.
My work gave me an MSDN account (Visual Studio Professional), which offers older bootstrapper downloads, but does not offer full offline installation downloads for older releases.
How do I install VS2017 15.2 (or 15.1, or 15.0) when 15.3 has already been deployed by Microsoft?
There is support for downloading a prior version, but evidently you have to contact support for the link. None of the links on any of the pages I could find within the VisualStudio.com site referenced it.
Installing an earlier release of Visual Studio 2017
Be sure to take the time to read the "[no]support policy" regarding "earlier" releases. Essentially, the day they released version 15.4, version 15.3.5 was no longer supported.
On another note, I have noticed many people seem to respond (here and on other similar postings) along the lines of "Why on earth would you want to reinstall the same version you were working with instead of the latest release?". Note that I am para-phrasing that to clarify the sentiments commonly expressed.
The reason is because TEAMS of developers need to be on the SAME version of the tool set. They have deadlines and cannot afford to drop everything and switch everybody to a new version of the tools that may or may not work correctly for them. Even if the developers were willing to take that hit to their productivity, usually their managers are not. This is why taking away the option to install the previous version the very same day you make a new release available is an unacceptable practice for Enterprise or Professional grade development software.
Another common reason is that when bugs have to be fixed in software, you often need to use the same, or very close to same, version of the tools to rebuild it after fixing the bug. The costs of regression testing after forcing a non-trivial upgrade on an entire software product or suite is unacceptable to most organizations. Upgrading may not even be an option due to contractual obligations.
It seems that based on this article that Microsoft do not offer a mechanism to download any version of Visual Studio 2017.
The https://my.visualstudio.com site offers bootstrap downloaders for 15.0 and 15.3 only. Intermediate versions such as 15.1 and 15.2 are not available as of September 2017.
I have a modest sized engineering team that would quite like to stay with 15.2 even for new starts and this is quite frustrating as we didn't capture an offline install of anything other than 15.0!
Apparently its possible to install a older version in parallel to a newer one. I just downloaded 15.6.7 from https://learn.microsoft.com/en-us/visualstudio/productinfo/installing-an-earlier-release-of-vs2017 and started the install - it didnt touch my existing installation 15.9.19
But the probably better solution is just to install the toolset which is available separately for each VC2017 release. See this intersting article:
https://devblogs.microsoft.com/cppblog/side-by-side-minor-version-msvc-toolsets-in-visual-studio-2017/
I am using AnkhSVN v2.5 and TortoiseSVN 1.9.4
I am not able to browse through the directories on my local drive.
Running as administrator didn't help either. However when using VisualSVN the issue is resolved.
Unfortunately, I can only use AnkhSVN, please help.
TortoiseSVN 1.9.x is based on Subversion 1.9. Local repository it creates and that you access via file:/// has FSFS format 7, by default. This FSFS format is new in SVN 1.9; SVN 1.8 and older clients and servers will not be able to read this repository unless you dump-load its data into an clean repository with older format.
AnkhSVN 2.5.x is based on SVN 1.8 (via SharpSVN) and this explains why it is unable to access this repository. The problem is that AnkhSVN does not display full error message in your case. The error could help you find out what's going on. I'm not sure, but I guess that this is the error that AnkhSVN had to display in your case: svnadmin: E125006: 'REPOS\db\format' contains invalid filesystem format option 'addressing physical'.
These steps should help you solve the problem:
Install VisualSVN Server or another Subversion server on Windows and access your repositories via HTTP(S) or svnserve instead of local file:/// access. The repository internals will not matter for your client in this case as the client will communicate with the server, not with the repository directly. This will help you avoid such problems in future.
Update to AnkhSVN 2.6.x. It should be compatible with SVN 1.9.x and Visual Studio 2012. I guess will access that repository without errors. I'm not sure, but I guess that there is no practical reason to use older AnkhSVN builds.
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.
I cant seem to compare two JS files (one edited locally and the latest version from the repository when doing Team Synch or Compare With) using Subversion in IBM RAD 7. I have used Subclipse as a plugin version 1.6.8.
I have totally downgraded to Subclipse 1.6.5 because my team mate's IDE (also RAD 7) is working fine on this subclipse version when comparing JS files.
I have also looked up and seems we have both the same version of RAD 7.
Frantically looked for solutions on the net and found nothing.
Sorry if this is the place to look for support. I was attempting to upgrade my RAD but darn the fix packs are so huge even for a little fixes (other fixes I mean)(shoo IBM).
Does anyone have a workaround?
I cant find the workaround so I just patiently downloaded the updates from IBM sigh.
Updating to RAD 7.5.5 fixes the problem