-
Notifications
You must be signed in to change notification settings - Fork 655
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
Simplify name of attach to process command #7167
Comments
I think we should change it. This comes down to a tradeoff:
I'm in camp 2. We can rely on docs to explain support. |
I forget what failure looks like if you try and attach to a .NET Framework process. As long as we have some sort of reasonable failure message, I think it is okay to change it. |
@gregg-miskelly This is the current error message: |
Can you try with an x64 .NET Framework process instead? |
It just hangs without any error message, it seems to be stuck:
|
Thanks. That is what I was afraid of. I personally think because of this we shouldn't name it "Debug: Attach to a .NET process" as there is almost no feedback what is wrong if you attach to a .NET Framework process. @richlander What do you think of "Debug: Attach to a .NET (6+) process"? |
Is there no way to detect and fail so we can call it .NET? |
I don't think we would want to error out in that case, since it is possible to host both .NET Framework and coreclr in the same process (not that this is a good idea). But we could warn I suppose. |
There should be no place where we say ".NET 5+ or .NET Core" in the Devkit UI. It's both because all the .NET Core versions are EOL but also because this phrasing is just unnecessary and confusing. It's also makes us look a bit silly.
The text was updated successfully, but these errors were encountered: