Search

MTM and Team explorer Work item query error by RKrishnan

Closed
as Not Reproducible Help for as Not Reproducible

2
0
Sign in
to vote
Type: Bug
ID: 780153
Opened: 2/27/2013 1:43:57 PM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug

In MTM when I try to create a test case for a requirement or in VS 2012 team explorer when I run a work item query I get the following error.

Method 'TryGetRowSet' in type 'Microsoft.TeamFoundation.WorkItemTracking.Client.ProxyRowSetCollectionHelper' from assembly 'Microsoft.TeamFoundation.WorkItemTracking.Client, Version=11.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' does not have an implementation.
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

Steps to reproduce

Connect to Team explorer
Open work item query
Run PBI query

Product Language

English

Operating System

Windows 8

Operating System Language

English

Actual results

Unable to add test cases in MTM
Work item query error in VS 2012

Expected results

Add Test cases in MTM
No error when connecting to team explorer to query work item
File Attachments
File Name Submitted By Submitted On File Size  
VS12bug.docx 2/27/2013 102 KB
Sign in to post a comment.
Posted by Microsoft on 2/28/2013 at 12:59 PM
Hi Krishnan,

We weren't able to reproduce the issue you're seeing. Can you contact me directly over email at hakane /at/ microsoft so I can investigate what might be wrong?

For now, I'm going to mark this issue as closed. If it turns out to be a bug, I'll reactivate.

Thanks,

-Hakan Eskici
Team Foundation Server
Posted by Microsoft on 2/28/2013 at 12:15 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 2/27/2013 at 1:50 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.