NullReferenceException showing properties of executable project if inside solution folder - by Carlos J. Quintero

Status : 


Sign in
to vote
ID 804338 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 10/2/2013 10:52:35 AM
Access Restriction Public


Sometimes you may want to use the Add > Existing Project context menu of the Solution Explorer to add an executable as a project to the solution. For example, to force the debugger type (2.0, 4.0, etc.) for an add-in of such executable as described in Procedure 3 at:

HOWTO: Debug an add-in for the VBA editor (32-bit or 64-bit) of Office with Visual Studio .NET.

It happens that you add the executable inside a solution folder, you can't show its properties page. If you add it inside the solution node, you can.
Sign in to post a comment.
Posted by Microsoft on 10/7/2013 at 11:07 AM
Thank you for the valuable feedback. Though we will not have a chance to address this issue in Visual Studio 2012, we will consider this feedback when planning for future versions of Visual Studio. Investments in this area will be weighed against the impact of other customer reported issues.
Posted by Microsoft on 10/3/2013 at 9:36 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 10/3/2013 at 7:21 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(