The command is "dotnet", with dot spelled out, and no uppercase N.
Regards,
James Scholes
On 03/11/2022 at 11:56, jacob kruger wrote:
Trying to play around with C# under VS code, as a form of reminder and for** To leave the list, click on the immediately-following link:-
example, the following bit of tutorial material from learn.microsoft.com
refers to using what I think is part of the .Net SDK, to initiate the
code/project/folder - .Net cli command:
Create a .NET console application using Visual Studio Code
<https://learn.microsoft.com/en-us/dotnet/core/tutorials/with-visual-studio-code?pivots=dotnet-6-0>
Anyway, the issue is that I am then getting the following error message when
I try execute .Net cli from command line to initiate part of the process:
'.Net' is not recognized as an internal or external command,
operable program or batch file
I have followed what I think are guidelines in installing the dotnet SDK,
etc., as well as the dotnet coding pack, which was referred to in another
form of tutorial material on a similar subject:
Using .NET in Visual Studio Code
<https://code.visualstudio.com/docs/languages/dotnet>
But, same issue?
Only referrals seem to find via google searches, etc. relate to a
command-line utility that is actually spelled out as dotnet, instead of .Net,
so, was just wondering if am missing something, if things like the fact that
also have a version of visual studio community edition installed alongside VS
code, etc. etc., could be causing hassles, or if there's just a location I in
fact need to add to my %path% variables collection, etc.?
For example, f ask the fully-spelled-out dotnet command line utility to tell
me --version, it tells me:
6.0.402
But, it just tells me am using incorrect argument if then tell it to process
CLI.
And, this is all under windows 10 64 bit Version 22H2 (OS Build 19045.2193),
in case that could be relevant.
Jacob Kruger
+2782 413 4791
"Resistance is futile...but, acceptance is versatile..."
