Hi,

I think I have explained before that microsoft introduced a new versioning and installer system common for all visual studio extensions. The management panel is available via tools>extensions and updates. This is where visual micro is installed/uninstalled and incremental updates can be viewed not just for visual micro but all extensions. 

The internal help>about system for visual studio has it;s own, different way to establish a version. You should direct any complaint about the help>about to microsoft thanks.

Since your last complaint about the version i changed the info message for the Major and Minor tools>options versions to clearly state the version can be ignored in this location and that you should use tools>extensions and updates.

I also explained to you that many users don't see the "updates available flag" at the top of the ide so visual micro uses another mechanism to notify major updates every few months via a dialog. This is why we still have tools options.

I am short of time and I would appreciate if we can avoid discussing the version number location again in the future. It also confuses the real purpose of your post which is slightly confusing.

Maybe an option for a full scan when a project opens could be added but it would cause complaints from our many pedantic users so would be an option

It's also possible that by exploring the shared library project system you can configure VS intellisense to be happier. We try to walk the best line between real arduino compile and vs c++ intellisense. It's a fine balance and the compiler has to be the thing that is right. 

You have stated that "Tools>Toggle Hidden Files" allows intellisense to be happier. That's one of its purposes.

Yes the build fortifies intellisense where it can because vs doesn't know about disconnected non-standard ardyuino magic include paths.

I think you have said that the build cache ensures intellisense remains corrected even after ide restart or re-open project. That, after a build,  intellisense only breaks if you clean the temp build folder or radically change library structure? Is this correct?

In what you have said is there anything you consider was working in previous build that is not now working?

Hi,

Generally it is correct that after a build intellisense is more accurate. This means that if you add a library that requires deep search to discover includes you MUST either build or #include the required <header> in the .ino.

There should be an automatic routine running that detects changes to .ino code and ensures intellisense is correct based on .ino #includes. This is a simple lightweight routine that does not cause slowness when editing files. Automatically performing deep search would be too slow (but maybe can be a future option for users to enable if they want it).

Your tests of deleting files in the temp folder are not practical and have no meaning. If you want a clean build then click Solution>Clean. If you want to preserve intellisense from the last build then do not use Build>Clean and do not mess with the temp folder.

Quote:


I will look at this, I suspect that the wavy lines would disappear eventually but vs 2017 is not perfect yet.

Quote:


Same as previous point. More likely to be a vs refresh issue but I will try it over the next couple of weeks

Great thanks

Build>Clean is best way to delete the temp then Build.