Macro $(ItemPath) sends path to a wrong file - by Andray Siletsky

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


4
0
Sign in
to vote
ID 761709 Comments
Status Closed Workarounds
Type Bug Repros 2
Opened 9/7/2012 4:36:48 PM
Access Restriction Public

Description

when starting External tools:
if the curren active document is not the open project item, the VS sends a path of the last open item of the open project to external tools. 
Sign in to post a comment.
Posted by Microsoft on 4/29/2014 at 12:32 PM
Thank you for reporting this issue. This issue has been fixed in Visual Studio 2013. You can install a trial version of Visual Studio 2013 with the fix from: http://go.microsoft.com/?linkid=9832436
Posted by Microsoft on 2/6/2013 at 3:28 PM
We unfortunately do not comment on the availability of fixes through Connect. For now, I would suggest to work around the issue if this is blocking you from doing work.

I have reviewed 703446 and will take note as we prioritize this issue in our backlog.

Thanks
Carl
Posted by ptousig on 1/31/2013 at 10:58 AM
Any ETA?

I want to know if I need to invest time in writing some kind of add-in to work around this bug.
It makes VS very hard to use for me. I rely on external tools a lot.

While you're at it, can you fix 703446 as well?
Posted by Microsoft on 1/13/2013 at 9:20 PM
We are considering a change for this issue for a future release of VIsual Studio. Thanks
Carl Brochu | Visual Studio Platform
Posted by Microsoft on 12/18/2012 at 10:33 AM
Hi,

Thanks for the feedback. This issue is on our backlog and we are investigating it. I will get back to you when we have an update or need help with the investigation.

Thanks!
Radhika Tadinada
Visual Studio Platform
Posted by Microsoft on 9/9/2012 at 9:06 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 9/7/2012 at 4:52 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)