I have my Visual Studio C# source code inside Microsoft Azure - Visual Studio Online (VSO), which is basically Team Foundation Server (TFS) 2013 in a Cloud. The Project was created using Microsoft Visual Studio Scrum 2013.3 Process Template.
I need to change process template from current (Scrum) to native Microsoft Visual Studio Agile 2013.3 Process Template.
Currently I do have only source code inside VSO and need to preserve all versions/check ins, with date/times and owners for whole team, there are NO any work items (tasks, bugs etc.)
One solution is to open a new Project inside VSO with Agile template, however how to migrate my code? or how to make simple / easy changes to current VSO project to change process template?
Create a new project and branch your code to the new project. The old project must remain to maintain history
use the TFS Integration tools to replay history against the new location.
(recommended) Switch to Git and use Git-TF to pull the history into git.
check out the tip and check into the new project.
The only option here that adds future value is to move to Git. Once there your history will be forever portable.
Related
I have a team working on a client-side node.js application. The sources are stored in a source control. I'd like to modify and debug this application in Visual Studio 2015. They use other IDEs, and I would not like to add additional VS-specific files such as .sln to source control.
I'm able to clone the repository, create a separate empty solution and add the repository as an "Existing Web Site". However, Visual Studio do not recognize package.json, and do not install dependencies as it would for MVC6 projects. Consequently gruntfile.js would not work either.
Is there any way to make Visual Studio see and process package.json, or I'm on a wrong track here?
Instead of using the "Existing Web Site" option, create a new solution and add items to it. Web Site Projects types are a different, legacy project type.
Since yesterday I am using the TFS of Visual Studio.
I have a webserver where I installed the TFS server with SQL Server 2012 express.
Everything is working perfectly but I do have 1 question.
I have created a workspace on my laptop which is then linked to a team project on TFS.
What do I do if my laptop crashes? Are my files of my workspace copied to the TFS server when you do a sign in in Visual studio?
Or do I need to use SVN repository like Tortoise to copy my projectfiles aside the TFS?
A workspace is a local working copy of the code. TFS will act as a code repository in the same way as SVN does.
you should be able to view the code that is checked in to TFS by using the source control viewer.
the basic process is
Create files in your local workspace
When you are happy commit them to TFS by using the check-in command
you can the edit / delete / add items to source control either by using the source control window, or the command line implementations.
you can find more information here http://msdn.microsoft.com/en-us/library/hh301771(v=vs.110).aspx#AddSource
I'm automatically publishing a web project after build from TFS 2012 by using a publishing profile (I have a build definition on TFS that has /p:DeployOnBuild,PublishProfile... etc. as additional MSBuild arguments). Everything works fine. However, since my web site creates some temporary local folders I'd like to clean up before the next automatic deployment. Is there a way to easily clean up? Maybe some additional MSBuild argument?
You should switch to using Release Management for Visual Studio 2013. I have had it Woking fore more than one customer with 2012. You can then create orchestration that is specifically designed for deployment rather than compilation.
Release Management with Visual Studio 2013
Our team has been having quite a lot of trouble with Visual Studio's publish feature. We use TFS and are all running VS 2012 ultimate. It works fine when only one person is involved in a project, but when we get many people inside one project, the publish profiles get off and Visual Studio reports a successful publish even when all files haven't been copied up. I've read all the SO questions about why this happens and I understand that TFS adds the publish profiles to the source control automatically. If we create a new publish profile and republish, everything works. But this is not sustainable. I can't prevent VS from automatically adding the publish profiles to TFS (if we could, I think this would solve the problem) so I'm now looking for better ways to publish an application to a web server. Is there a better tool out there to publish web applications or do I need to write my own VS extension?
Per this question (https://stackoverflow.com/a/12393154)
The temporary answer seems to be to change your settings from release to debug, save, then switch it back. This causes the pubxml.user file to be rebuilt, which is actually the problem.
I'm looking around mysite.tfspreview.com and I can view individual files, but I couldnt find a download all or get solution option.
So if a colleague doesnt have Visual Studio 2010 available and they wish to download a solution from TFS Azure preview what are the available options?
You should be able to use the command line client in the Microsoft Team Explorer Everywhere 11 Beta. It's not a big download (11MB), but I don't think there is a way to download a source tree directly from tfspreview without a client unless a zip has been added. Other source control services work this way (github, jira etc)
You don't need visual studio, but you need Team Explore which is add-on for Visual Studio or can be stand alone, it exists on the TFS media (DVD) or ISO, once you install Team Explore, you can access TFS Preview using GUI or Command line, you can also install TFS Power Tool 11 Beta, that will give you windows shell integration, so the context menu of the windows (when right click) it will has command to interact with TFS, as #Simon said, you can install Team Explorer Everywhere 11 Beta, but this for none windows OS or for add-on for other IDEs
Visual Studio Online has provided a means to do this (partly). On the website, navigate to your project's 'CODE/Explorer' tab. Right-click on whatever source directory/branch you wish and click the Download as ZIP menu item.
This will download a snapshot of whatever it is you selected. While extracting this won't "magically" link the files back to Visual Studio Online (ie, changes made will not be able to be committed directly from Windows Explorer, etc) or give you direct access to history; it will retain any source control bindings in any Visual Studio projects. This may be a good or a bad thing, depending on your circumstances.