v0.9.39

Add (preview ) support for VS 2022

• Applied PR #79 and update build number to 0.9.39

• Fixed PR 79 to reference final builds of VS 2022 (aka dev17)

• VsChromium-0.9.39.vsix is for Visual Studio 2022 only

• VsChromium-Pre-VS2022-0.9.39.vsix is for Visual Studio 2017 and 2019 only.

v0.9.38

DO NOT USE - Use https://github.com/chromium/vs-chromium/releases/tag/v0.9.39 or later for VS 2022 support.

Add (preview ) support for VS 2022

• Applied PR #79 and update build number to 0.9.38

v0.9.37

Bug fixes

• #70 Revise default include/exclude patterns for Chromium enlistments
• #71 Text Search should not use "\" as an escape character

v0.9.36

Bug fixes

• #61 VsChromium search stops working after native find-in-files is performed in VS2019 16.5.2
• #64 VsChromium sometimes keeps projects open in VS2019
• #65 VsChromium never finishes opening a project (directory traversal)
• #66 VsChromium sometimes fails to load index for invalid directories
• #67 Solution Explorer sometimes throws exception loading children nodes
• #68 Visual Studio hangs when using Resharper and VsChromium with a large project open
• #69 VsChromium does not show banner when a new version is available

Note: This is the same release as v0.9.35, with an additional fix for issue #69

v0.9.35

Bug fixes

• #61 VsChromium search stops working after native find-in-files is performed in VS2019 16.5.2
• #64 VsChromium sometimes keeps projects open in VS2019
• #65 VsChromium never finishes opening a project (directory traversal)
• #66 VsChromium sometimes fails to load index for invalid directories
• #67 Solution Explorer sometimes throws exception loading children nodes
• #68 Visual Studio hangs when using Resharper and VsChromium with a large project open

Note: This is the same release as v0.9.34, with an additional fix for issue #61

v0.9.34

Bug fixes

• #61 VsChromium search stops working after native find-in-files is performed in VS2019 16.5.2
• #64 VsChromium sometimes keeps projects open in VS2019
• #65 VsChromium never finishes opening a project (directory traversal)
• #66 VsChromium sometimes fails to load index for invalid directories
• #67 Solution Explorer sometimes throws exception loading children nodes
• #68 Visual Studio hangs when using Resharper and VsChromium with a large project open

v0.9.33

• Address issue #47: Wait for 3 seconds before unloading index after .sln file is unloaded. This should make project/solution reload faster.

• Address issue #58: Use NtQueryDirectoryFile to improve performance of reading directories and files.

v0.9.32

This release addresses issues #55 and #56: Add support for file exclusion (e.g -*.txt) as well as exact file match (e.g. "BUILD") for searching files.

• To exclude file names from a Code Search, use the - prefix character. As before, use ; to enter multiple file name patterns.

  • For example: *.txt;-*test* includes all files with the txt extension, except for the files that contain the test sub-string.

• Double quotes can now be used to prevent implicitly surrounding simple searches with "*".

  • For example, "foo" results in matching files that are named exactly foo, and nothing else (i.e. foo.txt will not be included).

v0.9.31

Add support for VS 2019, remove support for VS 2013.

VS 2019 requires a new API for VsPackages (AsyncPackage). This API is only supported from VS 2015 and later. Starting with this release of VsChromium (v0.9.31), older version of VS (VS 2013 and earlier) are not supported anymore.

This release addresses issues #49 and #52.

This release has a minor regression: loading custom icons for known file extensions (e.g. .cs, .cpp, etc.) in the Code Search and Solution Explorer tool windows was based on an undocumented VS API that was removed starting VS 2015, so the icon shows as a generic "Text document" icon.

v0.9.30

v0.9.30 changes:

Save as 0.9.29 with a couple of minor bug fixes

v0.9.29 changes:

• Access to server info from Code Search toolbar button:

• Show detailed information about each project/directory:

• Show configuration files for the selected project:

• Access to project index details from Source Explorer content menu:

• Access to index details of a directory from Source Explorer content menu:

v0.9.27 changes:

• Implement back off policy when disk activity is very high. Code Search goes in pause/yield mode for about 1 minute before re-scanning the file system. This is useful when a build add/deletes a lot of directories in a very short amount of time.

• Decrease the file system watcher buffer size from 2MB to 16KB. This is because a 2MB buffer has a noticeable performance impact on the operating system when lots of files changes on a fast SSD. With the new back-off policy in place, we should still support fast build scenarios, but with near zero performance impact.

• Add a manual pause/resume button in the Code Search tool window. This is useful if more fined grained control is needed.

• The Index status area in the top-right corner of the Code Search toolwindow is now a clickable button that can be used to display detailed information about the status of the index server.

• The Index status area now includes the server status

  • Idle means the server is working regularly
  • Busy means the server is busy synchronizing with the file system
  • Pause means the server has been manually paused
  • Yield means the server has backed-off due to heavy disk activity and will restart in the next minute or so.

• Do not block the Visual Studio UI thread at startup when waiting for the Index Server to start. This is now completely asynchronous, whereas the wait could be a couple of seconds before.

• Improve performance of the full file system rescan (about 3x faster on SSD drives)

• Decrease managed heap memory usage. For a index of about 600,000 files and 200,000 directories, the managed heap usage was decreased from from 400MB to 140MB. The native heap usage remains the same (about 2.5GB).

• Added persistent logging in %LOCALAPPDATA%\VsChromium. Up to 10 files of 2MB files each are use for logging.

  • VsChromium.log is used for information/warning/error level logging.
  • VsChromium.errors.log is used for warning/error level logging only.

• Improve reliability of incremental index updates. Due to the asynchronous nature of the incremental updates, there was the possibility of ignoring file change events when updating the index. This should be fixed now.

• Minor changes to the UI of the Code Search toolwindow to make colors work better with Dark and Blue VS themes.