I’m pleased to announce Entrian Inline Watch 1.0.11, which now supports Visual Studio 2019 version 16.1. The previous release was erroneously marked as only working with 16.0 rather than all 16.x versions. Thanks, Cahit and target2.
I’m relieved to announce Entrian Source Search 1.7.18, which, when running under .NET Framework 4.8 within Visual Studio 2019, no longer appears as either a blank rectangle or an entertainingly transparent rectangle, through which you can see your desktop. Thanks, Mark, Martin, and Morten.
Please note that the Source Search tool window won’t appear where you last left it, the first time you see it after the upgrade. It’s effectively a new window as far as Visual Studio is concerned, so it will appear in a default place and you’ll need to dock it again.
I’m pleased to announce new versions of Entrian Source Search, Entrian Attach, and Entrian Inline Watch, all of which now fully support Visual Studio 2019.
Full support for Visual Studio 2019 means that all three extensions use background loading, so they won’t necessarily load as soon as Visual Studio loads, or as soon as your solution loads. They will load as soon as you trigger one of their commands, but otherwise there can be a few seconds’ delay, before Source Search starts indexing, or before Attach will attach to newly started processes. Neither you nor I get any control over this, I’m afraid.
As well as support for Visual Studio 2019, these releases include the following fixes and features:
Entrian Source Search:
You can no longer close a locked tab; you need to unlock it first. Thanks, Mary.
Closing a tab that was restored from a previous session now closes the correct tab rather than some other one. Thanks, Marius.
Fixed a crash when you start a search, right-click in the results before they update, then click a menu command after they update. Thanks, Jools.
I’m pleased to announce new versions of Entrian Source Search, Entrian Attach, and Entrian Inline Watch, all of which work with Visual Studio 2019 Preview.
These versions are not yet optimised for Visual Studio 2019, so they may cause deprecation warnings. There’ll be new versions available before the final release of VS 2019 that will fix those warnings.