Tag: VSTS / TFS
So something that you've probably noticed when using dev tools in the web and Visual Studio Code is that you can hit ctrl + enter and with this you may have noticed that in Visual Studio you can't do that. Below you'll see how you can add this to your IDE.
TYMHKON is something random that to me looks like it could be Japanese? Not sure what makes me think that when seeing it but what it really stands for is Things You May Have Known Or Not!
I've generally built libraries wrong by placing all binaries in the root and it's worked ok for now so why change it. I might also add that these libraries have been for internal use so no real reason for not doing this I guess.
Although I'm hoping everyone reading this doesn't need this I thought I'd share anyway. A little under a month ago Jeremy Epling (@jeremy_epling) posted on the Microsoft DevOps Blog about the New Navigation for Visual Studio Team Services. I'm not going to repeat the very detailed blog post but I am going to show you how to enabled the amazing experience quickly.
I’ve probably mentioned it before but keeping up with what’s happening with VSTS is incredible hard with their 3 week cadence and generally huge set of features each 3 weeks. This week at MVP Summit I had what I thought would be a cool request to allow wild card branch policies. I was thinking of writing a console app to do this but thought it would be interesting to ask the product group as it’s part of the many benefits of being a MVP .
This is a quick reference post that shows you how to create a branch in VSTS and TFS.
If you have TFS on the domain but you are trying to connect agents to it from outside the domain and TFS is not running on https then this post is for you.
This post is largely showing off a cool feature of chrome but the core focus is how you can be more productive with VSTS search
With the rate that the VSTS team releases with all the features they releasing it's hard to know everything that exists in VSTS. I recently needed to migrate git repos from various Team Project Collections (TPC) into a single Team Project and started out doing it very manually and slowly progresses to importing over 100 in a couple hours .
You might be wondering after recently posting Setting up a standard continuous integration build with VSTS/TFS why I'd need to post specifically on .net core. After all it's still a Visual Studio solution so things should just work, the keyword here is should . Things didn't just work when I tried to get this working so decided to share my experience here (as well as document it for myself later ).
If you do a quick Google for pros of setting up continuous integration you'll come across a lot of articles about how good setting up continuous integration (CI) is compared to googling cons of setting up continuous integration which basically gives you the same posts of the the pros search so we won't dig too much into that now .
A couple weeks ago I was asked to present at DUT to a group of students. The presentation was quite a long one so I had to cut some bits out in order to present in the timeslot that I had. So I decided that I'd record all the content and post it up so that others can potentially benefit from it as well.
When I first heard about the SDK for widgets in Visual Studio Team Services (VSTS) I wanted to make a couple of widgets, one of these was a GitHub widget that would show some info from any GitHub repo on your VSTS dashboard. This can can be helpful when you have your source open on GitHub but still work out of VSTS.
So you could make a script that can do the bits below but if you don’t here is how you can easily create build agents fast for TFS 2015+ or VSO.
So if you haven't heard yet VSO Extensions are now in a private preview where you can sign up to get into the preview on extensions integration site. These extensions in the shortest sentence a supported way of doing customizations to VSO that will replace any of the "hacky" extensions that you may be playing around with at the moment like Tiago Pascal's Task Board Enhancer or maybe you have even created your own following similar steps to what I show in my TFS 2013 Customization book.
Ok so obviously the first you need is to have a VSO account. If you have one already, awesome, continue on and skip this section.
I use to make a lot of TFS customizations and had to apply the template changes to multiple team projects which took a bit of time. Depending on the method you use it could be a quick or loooong process . When I first started doing customizations I used the TFS Power Tools to upload changes which is a lot of effort because you are uploading one work item definition at a time into one team project.
This post has been ported from https://gbeeming.wordpress.com/2013/10/06/creating-fake-tfs-builds/.
TF400917: The current configuration is not valid for this feature. This feature cannot be used until you correct the configuration
UPDATE: This has been identified as a bug and will be fixed in the next release for on-premise
This post was originally found on my old blog at http://gbeeming.wordpress.com/2013/06/28/tf400324-team-foundation-services-are-not-available-from-server/.
So one of the benefits of using Server side Plugins is that you can't override them. The problem with this is that the users don't know that the policy is in place until they check-in their code. Wouldn't it be nice if me as a user were told this is what I need to do as in see the requirements from check-in policies but then to make the administrators or business rules that require the policies to also be happy.
So yesterday and update for Brian Keller's VM (Visual Studio 2013 Application Lifecycle Management Virtual Machine and Hands-on-Labs / Demo Scripts) was release
The other night while watching the Visual Studio 2013 Launch a question came up asking if the team had added support yet for automatically linking work items to the change set created when checking in as it currently is in Git. Currently this functionality doesn't exist for TFVC Check ins, at the time I didn't think anything of it but tonight for some reason I thought "hey that would be something simply to create and should hopefully make lives easier for developers". So I opened up Visual Studio and at the same time started a new project on GitHub for TFS Server Plugins. The code required for the plugin was very basic, basically just checked the comment from the check in with a regular expression and then added the links between the change set and all the IDs found in the comments.