I am using Visual Studio 2012 with TFS 2010, I want to use StyleCop checkin policy but it doesn't work. I have installed StyleCop, StyleCop Check-In Policy for TFS 2010 and Team Foundation Power Tools 2010 on server and client, still no benefit.
I know it's an older post but I just released a check-in policy for Visual Studio 2013. I don't know if you already using VS2013 but take a look at this extension. If you want VS2012 support, you can add an issue. If there are enough votes I will add support for it.
https://stylecopcheckinpolicy.codeplex.com/
Related
I need to migrate an old VSS 2005 source control database and I have downloaded & installed Microsoft Visual Studio Team Foundation Server Express 2015.
But I still have to use Visual Studio 2012 Professional (Reinstalled Team Explorer 2012 and then update 5). Trying to create a new project on TFS server throws error:
TF30172: You are trying to create a team project either without
required permission or with an older version of Team Explorer.
As I have added my account as TFS administrator I suppose the problem is with older version? Note that I have almost no experience with TFS, because I never needed it before. I cannot find any other means how to create a new project. (I planned to use this wizard).
Can I use TFS 2015 Express with Visual Studio 2012 Professional and if yes, how do I create a first empty project?
Yes, you are correct, only the latest version has "full" compatibility with the latest Team Foundation Server. You have to use the same Visual Studio of visual studio as the version of TFS that you're connecting to to create a team project.
If you're using TFS 2015 Update 2 or later then you can create a team project from the web as well.
Useful links:
https://www.visualstudio.com/zh-TW/docs/setup-admin/create-team-project
https://www.visualstudio.com/en-us/docs/setup-admin/requirements#client-compatibility
I am completely newbie to TFS. Need some help on Migration. We have a VS TFS 2015 and the requirement is to move a certain code with history and all the work items from current VS TFS 2015 to new VS TFS 2015. How can I achieve this. Any pointers will be of great help.
Just additional info. The current VS TFS 2015 was build by us on Azure and the new one is provisioned through Azure SAAS.
We don't widely support (as of August 3, 2016) importing your data from Team Foundation Server to Visual Studio Team Services. However, we have been working on a full-fidelity data import utility that will let you do this. It's currently in Private Preview and we're testing it out with a handful of customers at the moment. We've also shared some details with our Microsoft MVPs so if you have an MVP that is helping you, they will be able to help you migrate.
Feel free to vote on this User Voice item and we'll keep everyone updated there on our progress: Import data from TFS On-Premises
Tip: When the TFS to VSTS Data Import utility does become available, you'll want to make sure your TFS server is upgraded to the latest version of TFS including the latest update. At the moment, that would be Team Foundation Server 2015 Update 3.
You can use OpsHub Visual Studio Online Migration Utility.
OpsHub Visual Studio Migration Utility : Supports migration of source
code and work items from TFS 2010, TFS 2012, TFS 2013, and TFS 2015 to
Visual Studio Team Services.
I created a Custom Checkin policy and build it in Visual Studio 2013 and also build it in Visual Studio 2012 so that whoever using Vs 2012 can use the policy and successfully registered the policy to all machines. I applied the policy to a Team Project from my computer which has VS 2013. In our company some people still use VS 2012. Now whoever is using VS 2012 having issue on checkin. They get this error: Internal error in [Policy Name] policy. Error loading the [Policy Name] policy. Installation instructions: PLease see the web based installation instructions.
So does everybody in our company needs to upgrade to VS 2013?
Thanks for the help!
You should be able to remove the 2013 created policy and add it with 2012. It should then upscale to 2013.
Its the backward compat that's an issue...
The people with VS2012 should un-install 2013 version policy and install a policy with references to TFS2012 dlls.
I recently purchased a single user license for Visual Studio Online Professional in order to make use of the fact that it grants a monthly subscription license for the Visual Studio Professional IDE as well as all the features of basic VSO.
I ran into problems trying to apply the license to Visual Studio since VSO uses Azure Active Directory accounts to authenticate and these are not considered Microsoft Accounts. This means that when you go to Help -> Register and try to sign in you get an error telling you that it is not a MS account.
It appears that there is little or no documentation about this online.
To register a "Visual Studio Online" professional license within Visual Studio 2013 Professional ID you simply need to connect the trial version of Visual studio 2013 Professional to your Visual Studio Online TFS instance.
Note that this will not work if you have an MSDN license (either signin or product key applied to your Visual Studio 2013 IDE already. You must remove these first.
To remove a product key license from VS2013 please see the answer at https://stackoverflow.com/a/22258088/285470
Is there any way to get VS2012 set up for Enterprise Portal developing?
I already installed the EP Dev Kit for VS2010 and am able to build and deploy EP UserControls, but how to achieve this in VS2012?
MSDN says you have to use VS2010
Have I overseen something? Anybody knows about a workaround or something?
The complete solution and all referenced projects are built in VS2012 so it would be nice if there wasn't any need to have VS2010 involved for a single UserControl for AX.
As you said yourself, MSDN says:
Microsoft Visual Studio 2010 is required to create or modify User
Controls for Enterprise Portal
The visual studio components for AX don't work with VS2012 so you are stuck with VS2010. I don't know of any way to make it work but even if it was a workaround I would not recommend it since Microsoft says otherwise. You will not get support and you wouldn't be sure if any problems you face are due to using VS2012.
From that same page, these are the ones that are supported:
Visual Studio 2010 Professional, Visual Studio 2010 Premium, and
Visual Studio 2010 Ultimate.
It's not convenient but not a problem since you can run VS2010 and VS2012 side by side.