Timo

Forum Replies Created

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • in reply to: value of __cpluspluc macro in intellisense #35872
    Timo
    Participant

    I went the .vcxproj file route. Worked like a charm!

    For Posterity:

    I added a conditional property group

    <PropertyGroup Condition=”‘$(DesignTimeBuild)’!=””>

    <IntelliSenseCommandline>/Zc:__cplusplus</IntelliSenseCommandline>

    </PropertyGroup>

    Then i added the value of the property to the AdditionalOptions line

    <AdditionalOptions>-x c++ -fconcepts $(IntelliSenseCommandline) %(AdditionalOptions)</AdditionalOptions>

    Now it compiles and highlights correctly!

    Thank you for the quick support.

    in reply to: Intellisense always assumes c++14 #35729
    Timo
    Participant

    Hi,

    I copied the LanguageStandard attribute from a regular project and it worked like a charm.

    It even keeps the tags when you change project settings.

    Thank you very much for the swift assistancešŸ˜ƒ

    in reply to: Intellisense always assumes c++14 #35725
    Timo
    Participant

    Sorry for that, didn’t realize i was out of support. Should be renewed now.

    I would very much like to go ahead and try.

    in reply to: Intellisense always assumes c++14 #35718
    Timo
    Participant

    Im on VS 17.9.6.

    I created a Win32 Project, and the syntax highlighting worked as expected.

    I also created a different VisualGDB project (this time for an ARM-Based device), and the same problem appeared.

Viewing 4 posts - 1 through 4 (of 4 total)