Home Dashboard Directory Help
Search

$(ItemPath) wrong for external tools by Alecazam


Status: 

Closed
 as Fixed Help for as Fixed


4
0
Sign in
to vote
Type: Bug
ID: 773717
Opened: 12/6/2012 1:30:27 PM
Access Restriction: Public
0
Workaround(s)
view
1
User(s) can reproduce this bug

Description

VS2012 seems to randomly pick $(ItemPath) now. Among other uses, I use this for p4 edit command, and for a show in explorer command (why is this not in VS), and for jump to counterpart (why is this not in VS, jump to header doesn't jump back to .cpp). I use the p4 edit command since we have built-in source control disabled (too slow).

This has always worked in previous VS installs. If you select a source window, or select an item from the Solution Explorer, then $(ItemPath) should reflect that name.
Details
Sign in to post a comment.
Posted by Alin Constantin - MSFT on 1/11/2013 at 5:36 PM
I believe this is the same issue as http://connect.microsoft.com/VisualStudio/feedback/details/761709
(which we'll be fixing in a future release)
Posted by Microsoft on 12/17/2012 at 2:51 AM
Hi, given that we have not heard back from you in 7 days. We will go ahead and close this Connect Issue. If you get a chance to review and provide the information requested earlier, you can go ahead and reactivate this issue.
Posted by Clotharas on 12/14/2012 at 12:20 PM
I'm running into a similar issue, which I will submit using the Feedback Tool.

In my case the path it's returning isn't random, it's returning the correct path for items in the solution, but won't return the path of any item that isn't part of the solution. Instead it returns the path of the first open document that is part of the solution.
Posted by Microsoft on 12/12/2012 at 12:35 AM
Hello,

Sorry for bothering. Is there any update?

It would be greatly appreciated if you could provide us with that information as quickly as possible.

Thank you!
Posted by Microsoft on 12/7/2012 at 1:20 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please provide some screenshots to help us better understand this scenario?

Visual Studio now has an extension called Microsoft Visual Studio 2012 Feedback Tool, available on the VS gallery(http://visualstudiogallery.msdn.microsoft.com/f8a5aac8-0418-4f88-9d34-bdbe2c4cfe72).

The extension allows you to
1. upload files,
2. collect trace and dump files
3. collect steps while you're repro'ing the issue, as well as
4. SQM logs about VS extensions installed
5. System details (in DxDiag output)

Please submit this information to us within 4 business days. We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 12/6/2012 at 1: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.