v0.9.29

Same new features as 0.9.27 and 0.9.28, with support for displaying detailed information about index.

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.

v0.9.28

Same new features as 0.9.27, with a bug fix for files change notifications ignored when index is a Chromium repository.

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.

v0.9.27

• 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.

0.9.26

Bug Fix

• #42: VsChromium Code Search misses files after a directory rename

0.9.25

Update: Removed binary due to bug with file change notification ignored

Bug fixes:
#41: VsChromium sometimes performs full file system rescans
#40: VsChromium calls GetFileAttributesEx twice for files that are ignored

0.9.24

Fixes (minor) issues

• #35 VsChromium sometimes too aggressive at refreshing files
• #36 VsChromium sometimes rescans files too many times in a row

0.9.23

Add support for VS 2017 (no more warning at installation). VsChromium is now compatible with VS 2013, 2015 and 2017.

First version of VsChromium built with VS 2015 (instead of VS 2013).

Bug fixes:

• Fix bug #33: Adding support for VS 2017 (this required converting the VsChromium solution to be built with VS 2015)
• Fix bug #34: Refresh defaults for Chromium enlistments as Aug 2017.

0.9.22

Fixes issue #31: Read files with minimum locking behavior + Update Chromium defaults to avoid lock contention with clang intermediate files.

0.9.21

Fix VS debugger slow stepping when Source Explorer active

Minor bug fixes

• Fix issue #25: In Code Search result window, show number of results that would have been returned if Match case and Match whole word options had been disabled
• Fix issue #27: Improve navigation of search results within variable width encoding (utf-8, gbk) files