Intelli Sense Verbose: 4 : Formula Edit Update Edit State Formula editing: Current Prefix =su, Edit Window Bounds: 485,193,2075,66 Date Time=2016-12-07T.9030406Z Excel Dna. Excel Tool Tip Tool Tip Changed Received: Show:0x659458 with state: Formula Edit Date Time=2016-12-07T.9030406Z Excel Dna. Get Current Property Value(Automation Property property, Boolean ignore Default Value) at System. Also on Windows 10 Pro version with latest update from KB3206632 (OS Build 14393.576) - applied on December 14, but the issue has really only started today.Intelli Sense Verbose: 4 : Popup List window show Date Time=2016-12-07T.9040437Z Excel Dna. UPDATE: I'll note that if you persist with the block, and enter the name of function and start to provide argument values, the intellisense window that shows the names of the arguments and their descriptions remains performant, unless you do something to trigger the function intellisense window. So far it seems this problem is only with up-to-date Excel 2016 64-bit.Current Prefix: =, Thread 1 Not processing formula =n POPUPLISTWATCHER WINDOW CURRENT SELECTION System. Yes, 1.0.0 - I downloaded the latest version of the code before trying it in debug mode. More than happy to run more verbose debug tests if it will help (if you can indicate how)! Get Current Property Value(Automation Property property) at Excel Dna. Intelli Sense Warning: 4 : Popup List - Could not update selected item: System. I'll check some user's laptops to see if they are using the same version - they possibly are using older versions that aren't autoupdating - hopefully it is just my own workstation that has the issue at the moment as this makes the Intellisense add-in unusable unfortunately (which is a great shame as it makes our custom functions so much more usable and discoverable!My guess about the point in the code comes from just pressing the pause button on the debugger (and also checking later with breakpoints around it) Date Time=2016-12-07T.8811874Z Excel Dna. ) Our add-in does have a custom task pane that uses WPF, for what it is worth.Visual Studio 17 RC provides plenty of other great new features, and I recommend that you explore some of the other new changes to see how they integrate in your processes and workflow.Component One Studio's extensions work with Visual Studio 2017 RC, and we'll continue to improve and test our products so when production version ships, our controls will be ready to help make your transition as smooth as possible.I suspect that under the cover this also modifies the SUO file and solves the issue.
In addition, you'll see buttons at the bottom of the Intelli Sense window, and they allow you to further filter the results to only properties, events or methods.So the rule is: If you see some weird behavior in Visual Studio, try to delete the SUO file first, before you try anything else.