Replies: 1 comment 2 replies
-
WRT to #1546, I will just say, I was not upset, nor attacking you at all. There is something called, "dry humor". I don't agree with you, and you were really not reading my replies either. I wonder why you think I was being heated in one thread when I've not done so on any other of my replies? If you are getting emotional advice from a robot, I can see where you maybe struggle. :) By the way, why the double standard? Did you apply your robot to any of your replies? If you like, you can unlock that thread so that the bug can actually be useful and perhaps delete your replies. I can also remove mine and we could continue our discussion here. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Basically, dotnet should not be relied upon for this toolset. It is un-necessary and a poor design decision.
There is no guarantee that dotnet will be present on a particular system, especially while targeting older frameworks.
Possibly in future there may be redirections/additional restrictions in place on the usage (of that executable), the name may change, making using the library more difficult/error prone, etc.
@oleg-shilo If you like I can create a new bug/issue for a feature request for this.
Beta Was this translation helpful? Give feedback.
All reactions