visualSVN: Creating separate repositories for different versions of visual studio - visual-studio-2010

I've been working on a project with VisualSVN and Visual Studio 2010 for some time.
I recently upgraded my version of VisualSVN that supports Visual Studio 2012. I manually copied the project (that is not yet hooked into VisualSVN) to Visual Studio 2012 while keeping the old one.
I want to create a repo for the VS2012 version without colliding with the current 2010 version. I tried creating the new repo in a subfolder of the old one by copying the old one to a subfolder (using the repo browser from VS2010) and creating the new one in a subfolder itself (from VS2012). VisualSVN (or TortoiseSVN...) complained that the attempted location is in a previously created repo.
On local storage my file structure is:
/[Project Name]/Development/VS2010/[all files and folders]
/[Project Name]/Development/VS2012/[all files and folders]
I'd like to keep this structure in the repo.
Is this possible?

I've "solved" the problem by setting up TWO repositories:
/[Project Name]2010/[all files and folders]
/[Project Name]2012/[all files and folders]
This is a last-ditch effort. My original intent was to create branches under the Project, but that would interfere with the fact that the solution files are totally different content-wise but named exactly the same.

Related

New file in folder gets automatically added to TFS (TFVC) pending changes?

Team Foundation Server 2018 / Visual Studio Professional 2017 - Version 15.9.5
When i manually create a new file in Windows Explorer in a certain directory that is part of the TFVC source controlled tree, that file gets automatically added to TFVC pending changes (as "add"). Note that the file is not part of any project.
(The solution was opened in Visual Studio at the time the file was created).
This does not happen in other directories. I can add files to windows directories and they will NOT automatically be added to TFS and need to be manually added to TFS within VS Source Explorer. This is the expected behavior for me.
So it seems it is some configuration of a specific folder?, but i can't find it.
Didn't even know this was possible.
Can you tell me where to look?
FYI, this is a local workspace.
Edit: I have the TFS Explorer extension installed.
Edit: The new file is only added to pending changes when VS is open when creating the file in the folder. I did a test with VS closed, then create new file. Then reopen VS with solution and the file does NOT appear as a pending add.
When your workspace is configured as a Local workspace, files and folders are automatically detected and added (unless excluded by a .tfignore file).
Generally Local Workspaces are way more convenient, and are the default for workspaces with fewer than 100000 files (and with a fast system can exceed that number). It can be beneficial to configure a good tfIgnore file to control what is added automatically and what is ignored.
When there are no explicitly Included changes in your Team Explorer and you're in a local workspace, Visual Studio(2017+ from the to of my head) assumes you want to add all new changes and will auto-include them.
When your workspace is configured as a Server workspace, files and folders need to be manually added/removed, unless the changer are made through an IDE that is aware of the repository (Visual Studio will auto-add changes made in the solution explorer).
You can check the type of your workspace from the commandline:
tf workspaces /format:detailed /collection:https://dev.azure.com/jessehouwing
C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise>tf workspaces /format:detailed /collection:https://dev.azure.com/jessehouwing
=======================================================================================================================
Workspace : JACKIE
Owner : Jesse Houwing
Computer : JACKIE
Comment :
Collection : https://dev.azure.com/jessehouwing
Permissions: Private
Location : Local
File Time : Current
Working folders:
Or from Visual Studio:

Migrating from webstorm to Visual Studio 2015 - importing files from subversion using ankhsvn

I have been using the Webstorm trial version for a month and it has expired, so now I am considering using Visual Studio.
However, I have come across a stumbling block using ankhsvn, which is that I cannot figure out how to "import" files from existing files in subversion and add them to a project. Add to Subversion simply adds a new folder to the repo and I cannot see the existing files in the project explorer.
Is there a newbie friendly tutorial on how to import files from an existing svn repo to a solution in local space?
D'oh! Turns out I just needed to use Tortoise to check out the files, then create a blank solution in the same folder as the check out (this is important or ankhsvn won't play nice), and then add existing website to the project.

tfs $tf folder is missing from local workspace

I am trying to integrate our TFS with an external tool (Sonar) and for this Sonar needs the $tf folder that is supposedly (according to MS documentation) is supposed to exist on local workspaces.
I actually never seen this folder in any local environment before.
why am I not seeing this folder?
how can I have TFS/VS create it?
a few notes:
I looked for hidden files.
using VS 2010 premium / VS2013 premium and TFS2010
TFS and VS2010 don't support local workspaces. You'll need to upgrade both to at least 2012 (ideally, 2013) in order to use them.

Mercurial and the missing Visual Studio references

I'm rather new to Mercurial and i've just started a project on bitbucket with TortoiseHg. My project in in Visual Studio 2010. I'm able to commit changes to the mercurial without problem but when my team mate pull the project from the mercurial to work on it he get's references missing error. I was wondering if this is a bad config in my project or a missing references on his side?
The files that are referenced in your project are not going to be included in Mercurial, unless those files are contained within the repository.
Your colleague can find which references are missing by expanding theReferences folder in the solution explorer, and seeing which ones have a yellow warning triangle on them. You might need to the copy those missing files over to their machine.
Another option would be to place those referenced files (if appropriate) into a directory within your repository, then remove the reference from the project and re-reference from the new location. Then the files are be added to the repository, although it could bloat the repository, so not ideal if using remote central repositories.
I would also recommend VisualHG for Visual Studio to TortoiseHG integration, if you're not already aware of it.

Visual Studio and TortoiseHg: folder not visible in VS

I created a C# project and added it to source control (mercurial). I can edit files in VS, commit it and push it using TortoiseHg. It goes to the server. When some one pulls they get the files.
In my visual studio I added a folder and a file inside that folder. I used TortoiseHg and it saw the new file in the new folder. I committed it and pushed it.
However, now someone pulled the latest code from the server - and they got the new file (it is visible through windows explorer), but when they open the solution in VS, they don't see the file.
Does someone have an idea what is wrong here? or things I should check? Thank you for the help.
P.S. I have visual studio 2010 express (so I can't use the VisualHg plugin).
Visual Studio caches changes to the solution and project until an explicit save or a build. In your comment:
In my visual studio I added a folder and a file inside that folder. I used TortoiseHg and it saw the new file in the new folder. I committed it and pushed it.
I see that an updated .sln or .vcproj file was not mentioned and checked in. Did you see an update to either of these files via TortoiseHg? If not, make sure to build or save your project after a change like this.
Did you make sure that the Visual Studio Project File or Solution file is being updated and committed?
VS solution contains projects and each project select managed files by metadata(***.vcproj file). It's not the way include all files from root directory.
So, your co-workers can see new added files by in following two ways.
1) share project file(***.vcproj)
2) manually add files in each person's VS instance.

Resources