ikkentim / vs-tye-explorer

Tye Explorer for Visual Studio. Find running services, dive into service logs and attach your debugger to a services or specific replicas using a simple interface.

Tye Explorer for Visual Studio

I just really wanted to easily attach a debugger to a service run by Tye. So here's a quick and simple Visual Studio extension to do so.

Feel free to open an issue for bug reports or feature requests!

Features

• A simple overview of running services and replicas
• A shortcut to the Tye dashboard
• Show the output (logs) of a service
• Attach a debugger to:
  • a specific service
  • a specific replica
  • all running services (option to exclude specific services or replicas)
  • the startup projects of the loaded solution

Installing

The extension can be found on the Visual Studio Marketplace https://marketplace.visualstudio.com/items?itemName=ikkentim.TimsTyeExplorer22 . Install the extension through from the marketplace or directly from the extensions manager in Visual Studio.

How to use

• Run tye from your favorite command prompt
• Open the explorer through View -> Other Windows -> Tye Explorer

vs-tye-explorer's Issues

Care to release a new version of this extension?

With the latest updates onboard? :)

Make this available for VS 2022

Looks super useful! My team is currently on VS2022 where this extension is not yet available. Can we update this extension to VS2022 or is there anything blocking it? see: https://docs.microsoft.com/en-us/visualstudio/extensibility/migration/update-visual-studio-extension?view=vs-2022

If you're unable due to lack of time, do you accept a PR? (I can probably take a swing at this over the weekend)

Thanks!

Attach to startup project is unable to resolve a running tye service

When a project path is using a typical dotnet convention: Foo.Bar.csproj and a tye service name is using different casing convention such as foo-bar then this extension is unable to connect the 2.

Instead of matching the tye service by name which derives from the ProjectPath, we could match with the ProjectFilePath directly as configured in the tye.yaml

I'll introduce a PR shortly

Please Update Incompatible Tye Explorer Extension

Hi,

This is Leslie from the Visual Studio Extensibility team. I’m reaching out to you because we’ve received the following, high-priority feedback ticket for VS 2022: Visual Studio Feedback

We determined that this issue is the result of extension(s) not being updated to Visual Studio 2022 properly due to marking VS 2022 as compatible in the VSIX manifest but not referencing the new SDK PIA (Microsoft.VisualStudio.Interop.dll) and dependencies. We’ve identified that one of your extensions contributes to this issue:

• Tim's Tye Explorer

We strongly recommend that you update and re-publish your VSIX with the new VS 2022-compatible references, including EnvDTE.

Our investigation of the existing issue is that this happens when VS 2015 and VS 2022 are installed side by side, which is why it only occurred for a subset of customers. Nevertheless, referencing older versions of VSSDK assemblies is not supported, especially for the APIs and types that we’ve listed as breaking or altered. If you are doing so and find that your extensions work today, we make no guarantees that they will continue to work in the future. Extension authors could also find themselves in a situation where their extensions negatively impacts users due to untested workflows. From the product team’s perspective, we do not promise support to extension authors who do not follow our recommendation, and reference older versions of VSSDK. We also reserve the right to mark these extensions as incompatible should we find that VS is negatively affected by them. For the time being, instead of making VSIXValidator hard block any extensions that reference older assemblies, we will do a soft block and warn extension owners. And since this particular scenario is niche enough that it only affects side by side installs, we will not be marking them as incompatible, yet.

We will be pushing out changes in the coming months to warn both extension authors as well as extension consumers if they are creating or using an extension that are built with older versions of the VSSDK. We will share more details about this in the future.

Q: How can I validate whether my extension has dependencies on the old PIAs assembly?
A: You can try to validate the extension’s reference by following the steps below

1. Open the Developer command prompt.
2. Run the command ildasm as below.
   • C:>ildasm /text "{Extension Assembly}.dll" /output:result.txt
3. Check for references in the result.txt file.

For more info on how to migrate your extension to VS 2022 successfully, please view the following resources:
• Update Your Visual Studio Extension
• Breaking API List
• Migrated PIA List

Please email us if you have any questions.

Leslie Richardson
Program Manager – Visual Studio
[email protected] | @lyrichardson01