Search

Visual Studio 2012 does not see substituted drive letters by Talkersoft412

Closed
as Not Reproducible Help for as Not Reproducible

1
0
Sign in
 to vote
Type: Bug
ID: 776846
Opened: 1/17/2013 4:28:36 PM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
In visual studio 2012 if you launch it as administrator and go to file open, it will not see any drives that you mapped using the subst command.

for example, for flexibility over vpn we utilize a method in order to reference our assemblies locally, so we may map a link to a local folder on our hard drive which are a copy of the production assemblies. subst x: c:\tempassemblies. It works fine in visual studio 2008 and visual studio 2010, but does not work in visual studio 2012. I tried running it as administrator, i really can't think of anything else i can do in order to make this work.
Details (expand)

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

Visual Studio 2012

Steps to reproduce

1. map a drive letter to a folder on your local machine.
subst x: c:\tempassemblies

2. Open visual studio 2012 as administrator.

3. Choose the file open dialog, or create a new project and open up the add references dialog, try to browse for a file on your x: drive. You will not see it from either dialog.

Product Language

English

Operating System

Windows 7 SP1

Operating System Language

English

Actual results

not able to add or resolve references on an x: drive which is actually a mapped drive letter to a local folder.

Expected results

Being able to add or resolve references on an x: drive which is actually a mapped drive letter to a local folder.
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 2/7/2013 at 9:07 AM
Hi Talkersoft412. We haven't been able to repro this issue in our environments. Can you provide more information about the project types you are using, the vpn technology, the way you are using the subst tools and the paths you are using in add reference? Screen captures would be really helpful in determining the cause of this issue.

Thanks
Carl Brochu | Visual Studio Team
Posted by Talkersoft412 on 2/5/2013 at 10:09 AM
Yes i have tried this in both admin mode and not in admin mode, I have not found a solution to the issue. Could somebody just read the post and try and see if they are able to reproduce the issue? i have been able to reproduce the issue on 2 different windows 7 x64 machines.

Posted by Microsoft on 2/5/2013 at 9:41 AM
Since we have not heard back from you we will be resolving this issue as Not Repro. If you still need additional assistance with this issue, please let us know and we can reactivate this bug.
Thanks again for using Visual Studio!

Thanks,
Cathy Sullivan
Program Manager, Visual Studio IDE Experience Team
http://blogs.msdn.com/b/visualstudio
Posted by Microsoft on 1/21/2013 at 2:45 PM
Thanks for your quick reply. Can you try running Visual Studio without admin rights? Thanks!
Posted by Talkersoft412 on 1/21/2013 at 2:38 PM
yes I have launched it as administrator, you can see in my original bug report i specified that i launched it as administrator, i am pretty sure if there is a way to get it to work, i would have figured it out by now. I am running on x64 system windows 7.
Posted by Microsoft on 1/21/2013 at 2:04 PM
Thanks for using Visual Studio and reporting your issue. In order for this to work you should not run Visual Studio as an Administrator. If you don't run as Admin, are you still able to reproduce this issue?

Thanks,
Cathy Sullivan
VS IDE Team
Posted by Microsoft on 1/17/2013 at 8:28 PM
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 1/17/2013 at 4:51 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.
© 2013 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement