Home Dashboard Directory Help
Search

C++/CLI intellisense supprt cannot be enabled for makefile projects by jleidegren


Status: 

Closed


1
0
Sign in
to vote
Type: Bug
ID: 800758
Opened: 9/15/2013 12:35:38 AM
Access Restriction: Public
1
Workaround(s)
view
0
User(s) can reproduce this bug

Description

While Visual Studio 2013 has great C++/CLI intellisense support the current iteration does not respect the C++/CLI project setting of makefile projects. If you enable /clr support in the makefile project settings Visual Studio will still not recognize the syntax and you will get a lot of false postive C++/CLI syntax intellisense errors
Details
Sign in to post a comment.
Posted by Microsoft on 1/20/2014 at 10:57 AM
Hi,

Thank you for taking the time to provide your feedback. After reviewing your reported issue, in the context of all the issues reported to us, we have decided not to take any action on this feedback at this time.

Use a regular vcxproj file. Alternativelly we release an extension which may help you, the extension will allow you to get IntelliSense from a PDB file. Please look this up here:
http://visualstudiogallery.msdn.microsoft.com/952cac4e-fe4d-40a8-9656-9ae863bedbff

If this issue is severe, causing critical business situations or blocking your product development or deployment, please go to http://support.microsoft.com or call 1-800-MICROSOFT for assistance.
For Microsoft premier customers, please contact your administrator, your Technical Account Manager, or your Microsoft premier account representative.

Thanks,
Bogdan Mihalcea
VC++ Team
Posted by Microsoft on 1/20/2014 at 10:57 AM
Hi,

Thank you for taking the time to provide your feedback. After reviewing your reported issue, in the context of all the issues reported to us, we have decided not to take any action on this feedback at this time.

Use a regular vcxproj file. Alternativelly we release an extension which may help you, the extension will allow you to get IntelliSense from a PDB file. Please look this up here:
http://visualstudiogallery.msdn.microsoft.com/952cac4e-fe4d-40a8-9656-9ae863bedbff

If this issue is severe, causing critical business situations or blocking your product development or deployment, please go to http://support.microsoft.com or call 1-800-MICROSOFT for assistance.
For Microsoft premier customers, please contact your administrator, your Technical Account Manager, or your Microsoft premier account representative.

Thanks,
Bogdan Mihalcea
VC++ Team
Posted by jleidegren on 10/10/2013 at 2:13 AM
Sorry for reopening the issue, somewhat prematurely, the workaround described in the comments is just fine. Thanks for the assist.
Posted by jleidegren on 10/10/2013 at 1:57 AM
Hi, thanks for you response.

The workaround you suggested does not work. That was the nature of this bug report. I encourage you to try this out yourself and apologize if I wasn't clear on what I meant, in a makefile project you can't specify compiler specific switches through the project properties. While the additional IntelliSense options do exist, they don't work. This has to be a bug last I checked.
Posted by Microsoft on 9/23/2013 at 5:12 PM
Hi,

Thank you for taking the time to provide your feedback. After reviewing your reported issue, in the context of all the issues reported to us, we have decided not to take any action on this feedback at this time. We will re-consider our decision for a future release, in the meantime please consider accepting the following as a workaround to your problem: Please use the project properties to set new switches in IntelliSense as well (Configuration Properties -> NMake -> IntelliSense -> Additional Options).

If this issue is severe, causing critical business situations or blocking your product development or deployment, please go to http://support.microsoft.com or call 1-800-MICROSOFT for assistance.
For Microsoft premier customers, please contact your administrator, your Technical Account Manager, or your Microsoft premier account representative.

Thanks,
Bogdan Mihalcea
VC++ Team
Posted by Microsoft on 9/19/2013 at 7:23 PM
Hello again. We wanted to give you a quick reminder that to efficiently investigate and reproduce your issue, we need you submit the additional information we requested. We look forward to hearing from you with this information.
Posted by Microsoft on 9/16/2013 at 4:46 AM
Thanks for reporting the issue. In order to fix the issue, we must first reproduce the issue in our labs. We are unable to reproduce the issue with the steps you provided.

Please export and reset environment settings file by clicking Tools-> Import and Export Settings, after that, please zip the file and send it to us so that we can conduct further.

Please try this (from a Visual Studio command prompt with devenv in the path):
devenv /resetuserdata

Thanks,
Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 9/15/2013 at 12:52 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.
Posted by jleidegren on 10/10/2013 at 2:12 AM
As posted in the comments,

Configuration Properties -> NMake -> IntelliSense -> Additional Options and specifying /clr does seem to do the trick. Wasn't obvious at first but does work. Thanks for the info.