Updating intellisense slow
In Visual GDB 5.2 it can show variable assignments in a different color, distinguish references inside preprocessor macros and it’s now based on the WPF technology, making it much more responsive than the old window: You can download the preview version of Visual GDB 5.2 on the download page and explore the new features yourself.
The problem of course when you do this is that by default VS has no way of knowing that this script is available within the user control - and so won't provide intellisense of it for you.Devin is a BI consultant at Pragmatic Works Consulting.Previously, he has tech edited the book Professional Microsoft SQL Server 2008 Integration Services and was an author in the book Knight's 24-Hour Trainer: Microsoft SQL Server 2008 Integration Services.Two weeks ago we shipped a patch that you can apply to VS 2008 SP1 and VWD 2008 Express SP1 that causes Visual Studio to check for the presence of an optional "-vsdoc.js" file when a Java Script library is referenced, and if present to use this to drive the Java Script intellisense engine. We've worked with the j Query team to put together a j file that provides help comments and support for Java Script intellisense on chained j Query selector methods.These annotated "-vsdoc.js" files can include XML comments that provide help documentation for Java Script methods, as well as additional code intellisense hints for dynamic Java Script signatures that cannot automatically be inferred. You can download both j Query and the j Query-vsdoc file from the official download page on the j site: Save the file next to your file in your project (and make sure its naming prefix matches the jquery file name): You can then reference the standard jquery file with an html comment at the top of a standalone file.While being straight-forward, it could easily take considerable time and become annoying.So in Visual GDB 5.2 we have decided to automate this.Visual GDB 5.2 goes smarter about this by immediately showing the references discovered earlier and updating them once the last version of the file is reparsed.Another big annoyance reported by our users was the need to manually specify header search paths for imported projects.Each time Visual GDB discovers that some header files are missing, it will automatically search the nearby directories for those files.If some files cannot be located, you will get a chance to pinpoint them manually or just tell Visual GDB to scan another directory recursively and locate them there: Once the directories have been located, you can add them to your project properties (and to Intelli Sense properties) with on click of a mouse: If you are using GNU Make or CMake with Visual GDB-generated make files, it will insert the discovered directories there automatically, saving you more time: Another annoyance when working with complex C projects could be understanding the context of an error in a header file.