Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Support .NET #4

Open
olljanat opened this issue Apr 11, 2022 · 6 comments
Open

Feature Request: Support .NET #4

olljanat opened this issue Apr 11, 2022 · 6 comments
Labels
enhancement New feature or request

Comments

@olljanat
Copy link

It would be nice to have ready made debug tools container for .NET users too.

Some documentation about it can be found from:

@TomGranot TomGranot added the enhancement New feature or request label Apr 11, 2022
@TomGranot
Copy link
Contributor

Hey @olljanat - thanks for reaching out!

Marking this as enhancement, as it's something we're actively considering once we're done with the enhancements of the existing KoolKits.

I'll review the links, but any specific tools you'd like to see?

@olljanat
Copy link
Author

I don't have any specific tool in mind on this point.

@TomGranot
Copy link
Contributor

@olljanat No worries! We'll curate the list as we did for the other KoolKits. Thanks again for opening up this issue!

@artazar
Copy link

artazar commented May 23, 2022

Hi,
IMHO, the kool kit for dotnet should contain:
1 - All the debug dotnet tools like dotnet-dump, dotnet-trace, etc, basically everything from https://github.com/dotnet/diagnostics
2 - On top of that, dotnet-monitor to be able to capture data over http endpoint and also enable event-based captures via the collection list as described here.

@TomGranot
Copy link
Contributor

@artazar thanks a bunch for pitching in! I'll make sure to jot that down for our lists :)

@olljanat
Copy link
Author

olljanat commented Jul 2, 2022

I found also this article where they install vsdbg (process listening remote debug connections from Visual Studio) inside of container.

I think that it would make sense use it was main process on this image.

EDIT: It looks to be that vsdbg that works in way that communications between it and Visual Studio goes through console so it need to be different container image (and that is most probably outside of scope of this project).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants