A Visual Studio extension containing a collection of tools to help contributing code to the Chromium project.

Last update: Dec 30, 2022

Related tags

Overview

VsChromium

VsChromium is a Visual Studio Extension containing a collection of tools useful for editing, navigating and debugging code.

VsChromium was originally developed to help when contributing code to the Chromium project, but has evolved over time to become a more general purpose extension that can be useful for any project.

Amongst other things, VsChromium offers full text search engine, a fast and scalable alternative to the built-in "Find in Files" feature that can provide search results in less than 0.1 seconds for 100,000+ files.

See the Feature summary and Getting started sections for more information.

Documentation

Installation instructions

Comments

VsChromium search stops working after native find-in-files is performed in VS2019 16.5.2

Another issue with the same project setup as #60 (VsChromium-0.9.31, UE4 codebase with custom project config). Code search works until native visual studio find-in-files operation is done via ctrl+shift+f. All functionality stops working after that. Code search does not seem to perform any operations and opening VsChromium Indexing Server Information window gets stuck on "Please Wait" message.

Please let me know if there are any additional diagnostics / logs that I could provide to help you reproduce and investigate the issue.

opened by kayru 22
Wild memory usage and failing to index files with no apparent reason

I installed VS Chromium about 4 days ago and used it with no problems until today. Today I hit "Code Search" and noticed the index was empty and Vs Chromium was "Busy" reloading it. Note that I had not closed VS since yesterday (when it was working fine).

The indexing is still busy loading but remains totally empty, and looking at the Task Manager I noticed the RAM used by the plugin is oscillating wildly between ~1GB and ~5GB (it scales up from 1 to 5, then it resets to 1 and so on). Restarting Visual Studio doesn't change the plugin's behaviour.

I'm trying to index about 13500 files, fyi.

What baffles me is that this behaviour started with no apparent reason and no dramatic change in the project, and it's also happening to a colleague of mine who installed the plugin the same day as me. It's a particularly annoying situation, as this plugin was INCREDIBLY useful to replace the pathetic default File Search function, and I was enjoying the speedup a lot :(

opened by silverweed 13
VsChromium causes build breaks with clang-cl - updated filters needed

From a coworker's report:

If you build Chromium on Windows and run Visual Studio with VS-Chromium extension you may start seeing some seemingly random 'permission denied' errors during the build now that clang-cl is the default compiler.

This was investigated with PROCMON and it appears that the VS Chromium extension scans the source tree during the build and ends up reading temporary obj files created by clang.

Here are a few examples of files that can cause problems: dc_layer_overlay.obj-3b0874b9, V8ConstrainDoubleRange.obj-606e8091, typed_arrays_cc.pch-232411ff.

Because VS-Chromium doesn't recognize the file extensions it doesn't realize that these are files that should be excluded from scanning so it scans them, thus briefly holding a lock on them, thus causing build failures.

The workaround is to modify vs-chromium-project.txt to exclude .obj and .pch instead of *.obj and *.pch. This is easy enough for those who already have a vs-chromium-project.txt file, but tricky for others since creating such a file overrides the default filters and therefore can cause new problems. A workable vs-chromium-project.txt file with these modifications is attached - drop that in src\chromium\src to reconfigure VS-Chromium.

Building in these new filters would be very helpful.

vs-chromium-project.txt

opened by randomascii 12
File search should allow (linenum): suffix

Visual studio error/warnings contain the line number in parentheses at the end of the file path. This allows double-clicking to go to the file/line number. However if the error/warning is from a different machine or is partial (see https://code.google.com/p/chromium/issues/detail?id=440500#c189 and #c185 for examples) then navigating to the correct place in the code requires copy/paste of path into VsChromium, F8 to go there, then back to the source text to copy the line number, then back to VS, Ctrl+G, paste, enter to go to the line number.

If VsChromium understood the (linenum) syntax then it could ignore it during searches and go to that line number on F8/double-click.

It's a little bit inelegant, but the value is great enough to make it worthwhile overlooking this.

The colon that often follows the (linenum) should also be ignored if it is present.

opened by randomascii 7
Add support for excluding filenames for searches
There is already support for multiple file patterns in Code Search, e.g:

service_directory.cc;service_directory_client.cc

It would be nice to have the ability to allow excluding patterns, e.g.

service*.cc;-*test.cc

This would mean: include all files named service*.cc, except for the ones ending with test.cc

This also begs the question of the need for an escape character for "-"
opened by rpaquay 5
VsChromium needs updating for VS 2019

VsChromium works with VS 2019 Preview - for now. However it will stop working in the future. Details can be found here:

https://blogs.msdn.microsoft.com/visualstudio/2018/05/16/improving-the-responsiveness-of-critical-scenarios-by-updating-auto-load-behavior-for-extensions/

I followed the instructions and found this entry in the activity log:
618 2018/12/07 18:34:22.913 Warning SyncAutoLoadedExtensions Extension 'VsChromium' uses the 'synchronous auto-load' feature of Visual Studio. This feature will no longer be supported in a future Visual Studio 2019 update, at which point this extension will not work. Please contact the extension vendor to get an update. (UI Context: {f1536ef8-92ec-443c-9ed7-fdadf150da82} Package Guid: {a10cf7af-5f0a-4502-b44b-51ff1b7c8a87})

opened by randomascii 5
Support Ctrl+X for cut

I sometimes move a search term from the "Search Code" field to the "File Paths" field and I automatically try to do this with Ctrl+X/tab/Ctrl+V. But this doesn't work. I eventually remember that I have to do Ctrl+C/Del/tab/Ctrl+V. It would be nice to support Ctrl+X as well.

Not a big deal, just a nice-to-have.

opened by randomascii 5
VsChromium should visually indicate when it hits the maximum # of results

I just tried searching for "v8" (including the quotes) in one of my repos using VsChromium. The results vary from time to time. If I repeatedly paste in the string then the results keep changing.

It looks like VsChromium stops after the first 10,000 results, and the multi-threaded nature of the search means that the first 10,000 results are different every time, but there is not a great indication that the search was aborted.

I've hit variations on this issue a couple of times. It's not a bug, but some sort of indication that the results are partial would make it more obvious that the search should be constrained more heavily, or Tools-> Options should be used to increase the maximum number of results.

opened by randomascii 4
Release with .NET 4.5.2?

I have .NET 4.5.2 installed, yet vs-chromium won't install because I do not have 4.5 installed. The solution configuration targets .NET 4.5, not 4.5.2 - any reason why?

(sorry! I'm not a .NET developer, so I don't know anything about .NET releases)

opened by ariccio 4
Fix dependencies of VsChromium project

VsChromium, which includes the .vsix packaging step, should depend on all the other targets, except for the unittests.

This fixes the case where you open the project and build just "VsChromium," which was previously broken

opened by nick-chromium 4
Ignore error id 3 when indexing files.

This fixes issue https://github.com/chromium/vs-chromium/issues/5 which occurs in the presence of invalid NTFS junctions, apparently left behind from a submodules-based chromium checkout.

opened by nick-chromium 4
Default vs-chromium-project.txt hides some Chromium source files

The default vs-chromium-project.txt file - shown at https://github.com/chromium/vs-chromium/blob/master/vs-chromium-project.txt - contains a .ignore line of Debug/

Unfortunately that causes files such as base/debug/stack_trace_win.cc to be filtered out. This caused some confusion today when looking for Chromium's StackTrace class.

Either the filtering needs to be case-sensitive (not practical at this point except as opting-in for particular directories) or that line should be removed.

opened by randomascii 0
Security Policy violation Binary Artifacts
This issue was automatically created by Allstar.

Security Policy Violation Project is out of compliance with Binary Artifacts policy: binaries present in source code

Rule Description Binary Artifacts are an increased security risk in your repository. Binary artifacts cannot be reviewed, allowing the introduction of possibly obsolete or maliciously subverted executables. For more information see the Security Scorecards Documentation for Binary Artifacts.

Remediation Steps To remediate, remove the generated executable artifacts from the repository.

First 10 Artifacts Found

src/DkmIntegration/Microsoft.Dia.Interop.dll

src/packages/Microsoft.VisualStudio.Sdk.BuildTasks.14.0.14.0.215/tools/vssdk/Microsoft.VisualStudio.Sdk.BuildTasks.14.0.dll

src/packages/Microsoft.VisualStudio.Sdk.BuildTasks.14.0.14.0.215/tools/vssdk/Microsoft.VisualStudio.Sdk.BuildTasks.dll

src/packages/Microsoft.VisualStudio.Sdk.BuildTasks.14.0.14.0.215/tools/vssdk/Microsoft.VisualStudio.Setup.Common.dll

src/packages/Microsoft.VisualStudio.Sdk.BuildTasks.14.0.14.0.215/tools/vssdk/Newtonsoft.Json.dll

src/packages/NLog.4.4.12/lib/MonoAndroid10/NLog.dll

src/packages/NLog.4.4.12/lib/Xamarin.iOS10/NLog.dll

src/packages/NLog.4.4.12/lib/net35/NLog.dll

src/packages/NLog.4.4.12/lib/net40/NLog.dll

src/packages/NLog.4.4.12/lib/net45/NLog.dll

Run a Scorecards scan to see full list.

Additional Information This policy is drawn from Security Scorecards, which is a tool that scores a project's adherence to security best practices. You may wish to run a Scorecards scan directly on this repository for more details.

Allstar has been installed on all Google managed GitHub orgs. Policies are gradually being rolled out and enforced by the GOSST and OSPO teams. Learn more at http://go/allstar

This issue will auto resolve when the policy is in compliance.

Issue created by Allstar. See https://github.com/ossf/allstar/ for more information. For questions specific to the repository, please contact the owner or maintainer.
allstar
opened by google-allstar-prod[bot] 17
Not able to install VsChromium

I have installed Vs2022 Professional. While installing vschromium getting this error VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products.

dd_VSIXInstaller_20221111112621_2f98.log

opened by nileshk08 0
Link to latest is wrong for VS 2022

The VsChromium main page at https://chromium.github.io/vs-chromium/#installation links to https://github.com/chromium/vs-chromium/releases/tag/v0.9.37 as the latest release. However this doesn't work with VS 2022. Finding the correct release is non-obvious. Suggestions:

Update the main page to link to both the VS 2022 and previous-versions, with VS 2022 getting more prominent billing. Or, link directly to v0.9.39 since it looks like it supports all VS versions - just take away the pre-release tag.

v0.9.38 should probably be deleted.

opened by randomascii 0
Search Code doesn't auto-focus when vs-chromium is docked

Whenever I dock vs-chromium in VS 2019 and then proceed to unpin that docked tab (so it hides when I focus my code) - and then I proceed to Ctrl + Shift + ; it doesn't auto-focus the search field. When I undock vs-chromium and try again (even if I close that undocked window) - it properly focuses the field (up until I dock it again).

opened by 67protons 0

Releases(v0.9.39)

v0.9.39(Nov 19, 2021)
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.

Source code(tar.gz)
Source code(zip)
VsChromium-0.9.39.vsix(3.47 MB)
VsChromium-Pre-VS2022-0.9.39.vsix(3.31 MB)
v0.9.38(Nov 19, 2021)
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

Source code(tar.gz)
Source code(zip)
VsChromium-0.9.38.vsix(3.16 MB)
v0.9.37(Jun 26, 2020)
Bug fixes

#70 Revise default include/exclude patterns for Chromium enlistments

#71 Text Search should not use "\" as an escape character

Source code(tar.gz)
Source code(zip)
VsChromium-0.9.37.vsix(2.76 MB)
v0.9.36(Jun 22, 2020)
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
Source code(tar.gz)
Source code(zip)
VsChromium-0.9.36.vsix(2.76 MB)
v0.9.35(Jun 12, 2020)
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
Source code(tar.gz)
Source code(zip)
VsChromium-0.9.35.vsix(2.76 MB)
v0.9.34(Jun 9, 2020)
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

Source code(tar.gz)
Source code(zip)
VsChromium-0.9.34.vsix(2.75 MB)
v0.9.33(Feb 20, 2020)
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.

Source code(tar.gz)
Source code(zip)
VsChromium-0.9.33.vsix(2.75 MB)
v0.9.32(Feb 12, 2020)
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).

Source code(tar.gz)
Source code(zip)
VsChromium-0.9.32.vsix(2.75 MB)
v0.9.31(May 28, 2019)

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.
Source code(tar.gz)
Source code(zip)
VsChromium-0.9.31.vsix(2.76 MB)
v0.9.30(Feb 15, 2018)
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.

Source code(tar.gz)
Source code(zip)
VsChromium-0.9.30.vsix(2.73 MB)
v0.9.29(Feb 11, 2018)
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.

Source code(tar.gz)
Source code(zip)
VsChromium-0.9.29.vsix(2.73 MB)
v0.9.28(Feb 4, 2018)
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.

Source code(tar.gz)
Source code(zip)
VsChromium-0.9.28.vsix(2.69 MB)
v0.9.27(Jan 30, 2018)
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.

Source code(tar.gz)
Source code(zip)
VsChromium-0.9.27.vsix(2.69 MB)
v0.9.26(Dec 26, 2017)
Bug Fix

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

Source code(tar.gz)
Source code(zip)
VsChromium-0.9.26.vsix(2.42 MB)
v0.9.25(Dec 22, 2017)

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
Source code(tar.gz)
Source code(zip)
v0.9.24(Aug 8, 2017)
Fixes (minor) issues

#35 VsChromium sometimes too aggressive at refreshing files

#36 VsChromium sometimes rescans files too many times in a row

Source code(tar.gz)
Source code(zip)
VsChromium-0.9.24.vsix(1.90 MB)
v0.9.23(Aug 4, 2017)
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.

Source code(tar.gz)
Source code(zip)
VsChromium.vsix(1.90 MB)
v0.9.22(Aug 2, 2017)

Fixes issue #31: Read files with minimum locking behavior + Update Chromium defaults to avoid lock contention with clang intermediate files.
Source code(tar.gz)
Source code(zip)
VsChromium.vsix(2.30 MB)
v0.9.21(May 25, 2017)

Fix VS debugger slow stepping when Source Explorer active
Source code(tar.gz)
Source code(zip)
VsChromium.vsix(2.22 MB)
v0.9.20(Nov 18, 2016)
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

Source code(tar.gz)
Source code(zip)
VsChromium.vsix(2.32 MB)
v0.9.19(Nov 16, 2016)
Fix issue where server crashes when processing file system change notifications for path longer than MAX_PATH

Fix #25

Source code(tar.gz)
Source code(zip)
VsChromium.vsix(2.38 MB)
v0.9.18(Nov 19, 2015)
Fix long standing bug in binary file detection

Improve performance of binary file detection for large (i.e. larger than 200KB) files

Source code(tar.gz)
Source code(zip)
VsChromium.vsix(2.30 MB)
v0.9.17(Oct 6, 2015)
Implement suggestion in #21

Refine UI of code search result entries

Source code(tar.gz)
Source code(zip)
VsChromium.vsix(2.21 MB)
v0.9.16(Jun 25, 2015)

Minor bug fix: Size of index and memory usage sometimes not updated in "Code Search" window top left corner.
Source code(tar.gz)
Source code(zip)
VsChromium.vsix(2.29 MB)
v0.9.15(Jun 23, 2015)
Installation: Add support for VS 2015 RC and .NET 4.5.2

Tools | Options: add ability to change Fonts used by the Code Search tool window. Fixes issue #14.

Code Search: Automatically refresh the last search results after forcing a index refresh via the toolbar button.

Documentation: Various minor improvements and typos fixes

Source code(tar.gz)
Source code(zip)
VsChromium.vsix(2.29 MB)
v0.9.14(Mar 9, 2015)
Minor fix over 0.9.13, same release notes as 0.9.12:

Lots of UI changes and perf. improvements

"Official" support for indexing any directory in addition to Chromium enlistments

Simply create a vs-chromium-project.txt file at the root of the directory to index. See [https://github.com/chromium/vs-chromium/blob/master/vs-chromium-project.txt] for an example.

In addition, VS Chromium now tracks the solution file open in Visual Studio, so storing the vs-chromium-project.txt file next to the .sln file is usually enough to automatically enable indexing when opening a solution.

New Code Search tool window:

The tool window is used for performing text and file searches, and displaying/navigating results.

The tree view with files and directories has been moved to the standard VS "Solution Explorer" window, showing as "virtual" project nodes. This enables better integration with Visual Studio.

The former "Source Explorer" has been removed, as it is superseded by the changes above.

Tools|Options pages are now available for fine grained control over which VS Chroimum feature to enable or disable.

Quick Text Search productivity feature: Ctrl-Shift-; selects the current word in the current editor file, performs a text search on the selection and sets focus to Code Search window

Quick File Search productivity feature: Ctrl-Shift-' does the same for file paths.

Support Match whole word option

Support for "scoped" text search by specifying a path pattern in "File Paths" (e..g "/src" to restrict the search to files under the "src" directory)

Refresh search results when toolbar buttons are clicked

Updating the index is much faster when file changes (add/delete) occur on disk

Search results file location stay up to date with editor changes, i.e. when search results are displayed for a given file and changes are made to that file in the VS editor, double clicking on the search results will navigate to the updated location of the match

Auto-detect binary files and skip loading them

and more....

Source code(tar.gz)
Source code(zip)
VsChromium.vsix(2.29 MB)
v0.9.13(Mar 6, 2015)
Minor fixes over 0.9.12, same release notes as 0.9.12:

Lots of UI changes and perf. improvements

"Official" support for indexing any directory in addition to Chromium enlistments

Simply create a vs-chromium-project.txt file at the root of the directory to index. See [https://github.com/chromium/vs-chromium/blob/master/vs-chromium-project.txt] for an example.

In addition, VS Chromium now tracks the solution file open in Visual Studio, so storing the vs-chromium-project.txt file next to the .sln file is usually enough to automatically enable indexing when opening a solution.

New Code Search tool window:

The tool window is used for performing text and file searches, and displaying/navigating results.

The tree view with files and directories has been moved to the standard VS "Solution Explorer" window, showing as "virtual" project nodes. This enables better integration with Visual Studio.

The former "Source Explorer" has been removed, as it is superseded by the changes above.

Tools|Options pages are now available for fine grained control over which VS Chroimum feature to enable or disable.

Quick Text Search productivity feature: Ctrl-Shift-; selects the current word in the current editor file, performs a text search on the selection and sets focus to Code Search window

Quick File Search productivity feature: Ctrl-Shift-' does the same for file paths.

Support Match whole word option

Support for "scoped" text search by specifying a path pattern in "File Paths" (e..g "/src" to restrict the search to files under the "src" directory)

Refresh search results when toolbar buttons are clicked

Updating the index is much faster when file changes (add/delete) occur on disk

Search results file location stay up to date with editor changes, i.e. when search results are displayed for a given file and changes are made to that file in the VS editor, double clicking on the search results will navigate to the updated location of the match

Auto-detect binary files and skip loading them

and more....

Source code(tar.gz)
Source code(zip)
VsChromium.vsix(2.20 MB)
v0.9.12(Mar 2, 2015)
Lots of UI changes and perf. improvements

"Official" support for indexing any directory in addition to Chromium enlistments

Simply create a vs-chromium-project.txt file at the root of the directory to index. See [https://github.com/chromium/vs-chromium/blob/master/vs-chromium-project.txt] for an example.

In addition, VS Chromium now tracks the solution file open in Visual Studio, so storing the vs-chromium-project.txt file next to the .sln file is usually enough to automatically enable indexing when opening a solution.

New Code Search tool window:

The tool window is used for performing text and file searches, and displaying/navigating results.

The tree view with files and directories has been moved to the standard VS "Solution Explorer" window, showing as "virtual" project nodes. This enables better integration with Visual Studio.

The former "Source Explorer" has been removed, as it is superseded by the changes above.

Tools|Options pages are now available for fine grained control over which VS Chroimum feature to enable or disable.

Quick Text Search productivity feature: Ctrl-Shift-; selects the current word in the current editor file, performs a text search on the selection and sets focus to Code Search window

Quick File Search productivity feature: Ctrl-Shift-' does the same for file paths.

Support Match whole word option

Support for "scoped" text search by specifying a path pattern in "File Paths" (e..g "/src" to restrict the search to files under the "src" directory)

Refresh search results when toolbar buttons are clicked

Updating the index is much faster when file changes (add/delete) occur on disk

Search results file location stay up to date with editor changes, i.e. when search results are displayed for a given file and changes are made to that file in the VS editor, double clicking on the search results will navigate to the updated location of the match

Auto-detect binary files and skip loading them

and more....

Source code(tar.gz)
Source code(zip)
VsChromium.vsix(2.29 MB)
v0.9.11(Jan 22, 2015)
Finally Support regex searches for files names, folder names and text searches (find in files)

Performance seems to be around 3x-4x slower than plain text searches.

Fix long standing bug where text search results for files with UTF8 bom prefix would be 3 characters off.

Various minor UI tweaks, bug fixed and performance improvements.

Source code(tar.gz)
Source code(zip)
VsChromium.vsix(2.28 MB)
v0.9.10(Jan 14, 2015)
Ensure F8/Shift-F8 are captured only when Source Explorer window is visible and there is an active search result active. This is so that it doesn't interface with F8/Shift-F8 handling from other tool window.

Improve file path comparison performance and correctness

Improve caching of file contents de-duplication

Source code(tar.gz)
Source code(zip)
VsChromium.vsix(1.71 MB)