Can't seem to find an answer to this on MSDN or on here, does the Team Foundation Server 2013 API expose any methods to allow Project Creation? and if so in which classes?
No: project creation is a complex process involving many modules (DLLs). In fact, it requires Visual Studio (or Team Explorer) the same or newer version of TFS.
If you need to automate, you may use the tfpt createteamproject command line tool.
Update 2016-07-22: Since TFS 2015 Update 2 it is possible to create a project using the REST API.
Related
We use TFS 2015 vNext as our build system. However we use dotCover from JetBrains as our code coverage tool. The reason we don't use the built-in TFS code coverage tool is that this requires an Enterprise licence and we only have Professional licences (and upgrading is not an option).
Is it possible to display code coverage from a different code coverage tool to be displayed on the build results page in TFS 2015 (as in the screen shot below)?
Possible duplicate with this question Display OpenCover results in TFS 2015 build Summary .Your requirement could be achieved after TFS2015 update2.
If you want to display your custom result in the build result summary,
seems you will have to write your own extensions. Help link:
Overview of extensions for Visual Studio Team Services
Base for this were a lot of examples provided by MS on github:
Visual Studio Team Services Tasks
Visual Studio Team Services Sample Extensions
To get a first feeling what places on your TFS Web Portal can be
extended/customized you can download and install this extension
Contributions Guide from the Visual Studio Marketplace.
I have no idea/experience in VB programming. One of my client bought me his old project which need to be modified. He says it is written in Visual Basic and no idea which version.
So how can i carry ON to work with this project by identifying the version
And what other components do i require to do the programming and user interface.
I already have Visual studio 2010 with me. So can i do my work using this software or i have to go for anything else...
Any suggestions....?
Regards
ParshTest
You need to check the earlier VS version. If the project was developed in earlier version of VS, you can upgrade to VS 2010 easily but otherwise you need to get hands on specific VS version.
Similarly if the project have database functionality or crystal report or any other external dependencies, you need to check their versions. You need to install the components according to these versions. Specify your versions and i'll tell you what to use for further development.
I am testing web based products, and I am new to Microsoft tools. I am trying to figure out how test plan creation works, or can work depending on what configuration of Visual Studio tools I am using. I find a lot of conflicting info online.
I have the three tools below installed right now, but I can request something different if I need it. (Feel free to suggest). Any advice from pros more experienced with this tool set would be GREAT.
I access Team Foundation Server 2012 via my browser, where I can view and add product backlog items, bugs, sprints, the board etc. I cannot add test plans here, but I can add test cases to them.
I have Visual Studio 2013 installed on my PC. This seems like pretty much the same thing as the browser accessible tool, and I don't use it much because I find it easier to work from the browser for testing web.
I have Microsoft Test Manager 2012 installed on my PC. This appears to be the only place where I can create test plans, cases, and can create and utilize shared test case steps.
Questions:
How can I create test plans using the browser tool?
Is it possible to update the TFS 2012 Browser Tool to 2013, and how is that done?
Additionally to the #jessehouwing answer I would highly recommend you this free ebook:Testing for Continuous Delivery with Visual Studio 2012
Team Foundation Server 2012 update 2 adds Web Based test Case Management to TFS 2012, this is a smaller step than an upgrade to TFS 2013 all the way. You cannot just upgrade the Web Access part of a TFS installation, it would require a complete upgrade of the cluster. You also cannot just install this to your machine, it has to be installed on all the TFS servers in the cluster.
Traditionally Test Manager is the place to go to to do Test Suite Management and to view the results of a test run. Microsoft has started to move the functionality traditionally found in Test manager to the Web portal, It seems you're not the only person who found that easier to use. This transition started with TFS 2012 update 3 and was further expanded with TFS 2013.
So your options are:
Use Test Manager (you'll have to use it to manage certain things you cannot yet do on the web anyway).
Ask your Server Administrator to upgrade TFS 2012 to at least Update 2 (I'd recommend he upgrades to TFS 2012 update 4 or TFS 2013 in any case).
Ask your Server Administrator to upgrade TFS 2012 to TFS 2013.
The following resources can be very helpful in understandign how to use the tools to their fullest potential:
Visual Studio ALM Rangers' Test Guidance
Patterns & Practices' Testing for Continuous Delivery with Visual Studio 2012 (as mentioned by #Elena)
Microsoft Virtual Academy Software Testing with Visual Studio 2012 (exam 70-497 jump start)
I have written dozens of custom code analysis rules. The rules were developed targeting Visual Studio 2010. As required, the assembly has a reference to version 10.0 of FxCopSdk, Microsoft.Cci, and Microsoft.VisualStudio.CodeAnalysis. They run correctly in Visual Studio 2010 and build properly in TFS 2010.
I'd like to migrate to Visual Studio 2012. When I run the custom rules on an existing solution using VS 2012, however, I get CA0062 errors. The root cause is a CA0053 error loading the custom rules assembly. I understand that these references to the three assemblies need to be updated to version 11 for Visual Studio 2012. This can be done using version redirects in config files. I can get this to work locally by redirecting the Visual Studio 2012 IDE and FxCopCmd binaries, but am running into trouble when checking code into TFS 2010.
There are two apparent solutions we have considered, but neither is very palatable. The first is to require each developer to redirect locally, and then modify the TFS build agents to redirect as well. The second is to maintain two branches of the custom code analysis rules, one targeting version 10 (VS2010) and the other targeting version 11 (VS2012).
Is there a better way to do this, or do we need to all upgrade to TFS 2012 and Visual Studio 2012 simultaneously?
You can try to manually edit the project file and write two include blocks (one for VS2010 and one for VS2012), then define conditions to use the correct one. You only have to somehow determine if You want to build for VS2010 or VS2012 in msbuild.
Between your approaches and the one proposed by ZFE, you pretty much have all the potential candidates. Given the choices, I would strongly recommend branching since there is no official SDK for FxCop with backward-compatibility guarantees.
If you're lucky, you won't hit any behavioural or API surface changes that affect your rules, and the only difference between your two branches will be the references, so any merges will be trivial. However, any time investment you make in an alternate approach now will be lost if you need to branch later, and the likelihood of eventually needing to branch is non-negligeable.
I use TFS2010 for source control and a build agent on windows server 2008 R2 (x64) for continuous integration.
Recently, we introduced a lightweight client application X that uses Office 2007 Primary Interop Assemblies to interact with Excel. The app has many dependencies to various projects in the solution. No other project have any dependency to X.
This is all well and good except that X wont build on the build server. From reading a few blog posts and some posts here on StackOverflow, I understand that it is not advisable to attempt to install these PIA's on my x64 build server. And that doing so will involve a bit of hacking in registry.
The solution has more than 30 projects and I do not want to duplicate the .sln in order to create a bastard BuildServerVersion.sln (or something) that contains the 29 projects that I DO want to build on the build server.
Is there a simple way to either satisfy the dependencies to the Office 2007 PIAs or to make the build agent stop trying to build that particular project? I suppose we could build and deploy just app X from a developer machine. It is an internal tool, anyway.