Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
User name:
Password:
Save Password
Forgot your password?

 All Forums
 Visual Assist
 Technical Support
 VS2015 include header from VS2013
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

Mordachai
Tomato Guru

USA
224 Posts

Posted - Oct 06 2016 :  10:53:25 AM  Show Profile  Reply with Quote
Right clicking on "std::future" & requesting "insert header" gives me:

#include "..\..\..\..\..\..\Program Files (x86)\Microsoft Visual Studio 12.0\VC\include\future"

I already did the "clear cache" and "rebuild symbol" and restarted, then tried again.

Why didn't it do:

#include <future>

?

Is there something I'm missing someplace? What can I check?

Edited by - Mordachai on Oct 06 2016 2:33:00 PM

ChrisG
Whole Tomato Software

USA
162 Posts

Posted - Oct 06 2016 :  12:27:14 PM  Show Profile  Reply with Quote
Did you mean to title the thread, 'VS2015 include header from VS2013'?

Normally, I would ask you to try clicking 'Rebuild' and 'Clear' in the following menu.
(VAssistX | Visual Assist Options | Performance)

Then, restart your IDE.

However, since the issue still remains, try typing out the correct include like '#include <future>'. Then, delete the include and try to add the include through Add #include Directive. This could help ensure Visual Assist knows about the correct file.

Edited by - ChrisG on Oct 06 2016 12:30:23 PM
Go to Top of Page

Mordachai
Tomato Guru

USA
224 Posts

Posted - Oct 06 2016 :  2:33:55 PM  Show Profile  Reply with Quote
Sorry - yes - fixed the thread title :D
I did exactly that - typed the corrected one and intellisense / VA seem to seeing the correct thing.
I'll post here if I get anymore of this same behavior.
Go to Top of Page

ChrisG
Whole Tomato Software

USA
162 Posts

Posted - Oct 06 2016 :  6:12:13 PM  Show Profile  Reply with Quote
When you have both VS 2013 and VS 2015 installed there is a known issue where this can happen for certain symbols.

We plan to have some improvements in this area soon.
Go to Top of Page

Mordachai
Tomato Guru

USA
224 Posts

Posted - Oct 07 2016 :  3:04:54 PM  Show Profile  Reply with Quote
I found this confusion when I was working with "future" and "optional" - with 2015 update 3 - if that helps you at all.
Go to Top of Page

sean
Whole Tomato Software

USA
2698 Posts

Posted - Oct 19 2016 :  12:52:42 PM  Show Profile  Reply with Quote
I believe this is due to case=65910. It is fixed on our main line, but the fix did not go to the release branch for 2114. We'll try to get it on the release branch for next month.
Go to Top of Page

Mordachai
Tomato Guru

USA
224 Posts

Posted - Oct 19 2016 :  2:30:28 PM  Show Profile  Reply with Quote
I'd be happy to use a beta to verify that
Go to Top of Page

sean
Whole Tomato Software

USA
2698 Posts

Posted - Nov 30 2016 :  10:22:59 PM  Show Profile  Reply with Quote
Sorry -- this did not get fixed in build 2116. The fix that we had did make it to the release branch -- but testing failed. We'll revisit it and contact you once we have test dll.
Go to Top of Page

Mordachai
Tomato Guru

USA
224 Posts

Posted - Dec 01 2016 :  09:27:25 AM  Show Profile  Reply with Quote
Ah, bummer! Hopefully next build.
Go to Top of Page

sean
Whole Tomato Software

USA
2698 Posts

Posted - Mar 09 2017 :  12:10:38 AM  Show Profile  Reply with Quote
case=65910 is fixed in build 2210.
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
© 2019 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000