Mariusz, Gorzoch tech Blog

Archive for February 2014

Method TryGetRowSet not found

with one comment

Today I come across below error when trying to use TFS API on the machine where SDK is not installed at all.

Method not found: ‘Boolean Microsoft.TeamFoundation.WorkItemTracking.Proxy.IWorkItemRowSets.TryGetRowSet(System.String, Microsoft.TeamFoundation.WorkItemTracking.Proxy.IRowSet ByRef)’.

System.MissingMethodException: Method not found: ‘Boolean Microsoft.TeamFoundation.WorkItemTracking.Proxy.IWorkItemRowSets.TryGetRowSet(System.String, Microsoft.TeamFoundation.WorkItemTracking.Proxy.IRowSet ByRef)’.

My solution was build on the dedicated build server and then deployed to destination server thru WebDeploy.

I’ve look around for the solution for a while and then come to the post:


where someone pointed that Microsoft did a very bad think with update 2 for Visual Studio 2012. What it happened to be is that they adjusted version of the library “Microsoft.TeamFoundation.WorkItemTracking.Proxy.dll” to 11.0.60315.1, but they change it only in GAC and not in the official visual studio folder “C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\ReferenceAssemblies\v2.0”.

So, it work in the way that :

“C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\ReferenceAssemblies\v2.0” points that version of “Microsoft.TeamFoundation.WorkItemTracking.Proxy.dll” is “11.0.50727.1” where in reality our apps are looking into the GAC and using version “11.0.60315.1”.

In order to solve that problem you need to go to GAC folder  “C:\Windows\assembly\GAC_MSIL\Microsoft.TeamFoundation.WorkItemTracking.Proxy\” (you can just use windows console) and copy our proxy library from there to your project and explicitly reference it.

Doing above solve problem in my case


Written by Mariusz Gorzoch

27 February 2014 at 10:20

Posted in Bez kategorii

A device attached to the system is not functioning

with 2 comments

or if you prefer the full message:

Error Message:

A device attached to the system is not functioning. (Exception from HRESULT: 0x8007001F)

Stack Trace:
A device attached to the system is not functioning.

Our team get it when we were trying to certificate our Win8 app against Microsoft store. Before I get into detail’s let me give you some background:

Link to the app :   
Application was built with use of :  
Visual Studio 2012 Ultimate   
Windows 8.1  
We are targeting:  
Windows 8 , x64, x86, ARM devices  
Our app uses:  
We did so far 7 releases of the app and recently we had to introduce one emergency change into the app. That extra change was connected with removing automatic deletion of the reports (those with you can see on the main screen of the app) in case of some special conditions. That change was really simple one and should not affect at all stability of the app. Unfortunately even the release 7 went without any problem than the current release (=release 7 + some really simple change) cannot go thru certification process at all. According to the reports with we were getting from Microsoft testers our app crashes almost on the first screen (and if not there, then on the second screen). The thing is : that we cannot reproduce that at all and by this I mean:  
1.      We have tried our app on our corporate laptops “Latitude E6420”  
a.       Windows 8 x64 version of our app  
b.      Windows 8 x86 version of our app  
c.       Windows 8.1 x64 version of our app  
d.      Windows 8.1 x86 version of our app  
2.      We have tried our app on ASUS Vivo Tab RT (ARM version of our app)  
3.      Lenovo ultra-book : http://www.x-kom.pl/p/171366-ultrabook-13-3-lenovo-ibm-yoga-13-i5-3337u-8gb-128ssd-win8-pomaranczowy.html   
4.      Samsung device : http://www.tabletmaniak.pl/77329/test-samsung-ativ-smart-pc-500t/   
5.      Our app is used by numbers of users in Norway (they are using release 7 of the app)  
6.      Our app was tested by our colleagues in Holte-Norway   
and no one on our site report to us such a problem.

We were blind and we run out of ideas…and then one team member suggested that maybe we should try to build our solution based on Windows 8 (=not windows 8.1). He was the only one in our team who didn’t upgrade his machine yet. We tried that, and guess what : on the next day our app went thru Microsoft tests without any problem.

So, if you have similar problem then ensure that if you are using Visual Studio 2012 to build your app for Windows store, then you use Windows 8 and not Windows 8.1. Most probably this is some kind of bug on the Microsoft site, and maybe at the time when you read that this will be not relevant at all…but for now, it is… and we wasted around 2weeks to sort it out.

Written by Mariusz Gorzoch

6 February 2014 at 08:24