Search

Two users on a server cannot use Coded UI Test Builder at once by aletiro

Closed
as Deferred Help for as Deferred

1
0
Sign in
to vote
Type: Bug
ID: 779487
Opened: 2/19/2013 12:57:16 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
We are using Windows Server 2008 R2 and Visual Studio 2012 Ultimate (Update 1). When two users log on and one already has the Coded UI Test Builder open, the other can't open it. Instead an error message prompts to the user saying that he should close the Coded UI Test Builder first (which he never opened, but it's referring to the first user's CUIT Builder session).

If the two users are able to use Visual Studio simultaneously, they should also be able to use Coded UI Test Builder.
Details (expand)

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

Visual Studio 2012

Steps to reproduce

1. Log on with one user to a Windows Server 2008 R2 machine with RDP
2. Start Visual Studio 2012 Ultimate and open the Coded UI Test Builder
3. Log on with another RDP session to that server with a different user
4. Start Visual Studio 2012 Ultimate and open the Coded UI Test Builder

Error message appears

Product Language

English

Operating System

Windows Server 2008 R2

Operating System Language

English

Actual results

Error message appears to the second user stating that the user should close the Coded UI Test Builder first, even though he never opened it.
Coded UI Test Builder does not open.

Expected results

Coded UI Test Builder should open.
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 3/4/2013 at 12:58 AM
Hi aletiro ,
Thank you for reaching out to us. This capability doesn't exist today - we have added this suggestion to our product backlog.

Thanks,
Prachi
Posted by Microsoft on 2/20/2013 at 12:04 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/19/2013 at 1:51 AM
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.