.NET Core RC 2, TFS, and you in a pickle. “Failed to make the following project runnable” – Access Denied


Can’t touch this


This is basically an issue which is likely to happen (AFAIK) if you’re currently using Server Workspaces in TFS. Due to the size of the solutions and projects I’m working in, changing to a local workspace feels a lot slower. Now, I’ve recently switched some of my projects to .NET Core, and building one of them has yielded the offending error:

Failed to make the following project runnable: aaa.bbb.ccc (.NETFramework,Version=v4.5) reason: Access to the path ‘g:\xxx\yyy\zzz\bin\Release\net45\uvw.dll’ is denied.

This is caused by the fact that those files are marked as “read-only”, which is the default for files in source control that are not checked out. Click here to read more.

The end to all of your TF14098: Access Denied, or how to figure out wrong permissions (TFS2013)


But I do have permissions!


I’ve come across a pestering access issue on TFS2013 (On-Premises), where I couldn’t delete some branches because I had no access to path/*. After reviewing my permissions a thousand times on the accusing path, I almost gave up and used tf destroy to incinerate them. (PROTIP: don’t do that unless you ABSOLUTELY have to). Most of the times, this problem is caused by a permission set in some subfolder or file inside of the folder you’re willing to delete. The thing is: VS doesn’t tell you exactly what files have the treacherous permission set that drives you to insanity. Click here to read more.

Quick and dirty setup for tracking currently playing Spotify tracks (Only works with the PC app)

I am getting ready to participate in the next Ludum Dare (LD35), and being my first time, I wanted to do it on Twitch as well. So I started setting things up, such as adjusting my screen and webcam layout and getting some music. I’ve found that there was no easy way to show my current playing track on spotify. Not the way I wanted, anyway.


What have I tried?


First, I tried capturing the Spotify App windows partially, but it hides part of the song if it’s longer than the widget size. It was kinda ugly. Then, I tried using their api, but it seems there is not such method to get the current playing track. Without any further options, I noticed that the song/artist names showed up on the title of the window. So I’ve come up with a quick and dirty C# wpf app to capture the title and format it to my needs. Click here to read more.

A mild Caveat while reading the InputStream in a Custom TFS Plugin if you’re using Git as Source Control

This is related to the implementation of a custom plugin using ITeamFoundationRequestFilter.

You can go to the first part of my post series by clicking the link below:

https://conradoclarkdeveloper.com/2015/03/02/iteamfoundationrequestfilter-part1-tfs

This post is a fix to a possible problem while reading requests if you’re using Git.


The problem with InputStream


In my first posts about implementing ITeamFoundationRequestFilter, I’m using HttpContext.Current.Request.InputStream to read the contents of the request. It happens so that, depending on the implementation, this may break Git functionality. If you access the InputStream before trying to push content to git, the following error is shown: Click here to read more.

Same yet different. Getting information from a TFS Request (WebAccess JSON)

This is the third part of a series on how to implement a validation plugin using ITeamFoundationRequestFilter.

You can go to the first part by clicking the link below:

https://conradoclarkdeveloper.com/2015/03/02/iteamfoundationrequestfilter-part1-tfs

In this post I’ll explain how to handle work item create/update requests from WebAccess.


What’s in the request again ?


Last time we figured out what Visual Studio requests to TFS in order to create/update Work Items. With this information, we’ve created a simple validator which prevents a specific user from creating work items. It may work wonders when the request is being sent to the ClientService.asmx service as VS does, but unfortunately this kind of operation is not centralized, so if you try to create the work item through WebAccess, your validation just won’t work.

Keeping that in mind, we’re going to inspect WebAccess to figure out how does it creates/updates work items. It’s actually easier than before because we can see the request in the browser itself: Click here to read more.

Different yet the same. Getting information from a TFS Request (Soap XML)

This is the second part of a series on how to implement a validation plugin using ITeamFoundationRequestFilter.

You can go to the first part by clicking the link below:

https://conradoclarkdeveloper.com/2015/03/02/iteamfoundationrequestfilter-part1-tfs

In this post I’ll explain how to intercept a work item creation request and prevent the operation from executing.


What’s in the request ?


After creating a simple plugin using an ITeamFoundationRequestFilter implementation, you are now able to intercept requests to TFS.

I recommend using a software such as Fiddler to capture requests and observe what they’re like. In our case, we’re going to investigate what goes on when we create a WorkItem on Visual Studio and on Web Access. I’ll also be using Fiddler since it’s well known and easy to use. Click here to read more.