Проблема с Dotnet RU
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- csharp
- Domain
- documentation
Research direction
The issue reports that the dotnet command is not recognized on Windows while following the Russian Hello World tutorial. Start by locating the tutorial source in the dotnet/docs repository corresponding to the given URL. Add a prerequisite note about installing the .NET SDK. Verify the documentation builds.
Written by the indexing model from the issue text.
Description
URL
https://dotnet.microsoft.com/ru-ru/learn/dotnet/hello-world-tutorial/intro
Operating system
windows
More information about your system
dotnet
dotnet : Имя "dotnet" не распознано как имя командлета, функции, файла сценария или выполняемой программы. Проверьт
е правильность написания имени, а также наличие и правильность пути, после чего повторите попытку.
строка:1 знак:1
- dotnet
-
+ CategoryInfo : ObjectNotFound: (dotnet:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException помогите
Description
dotnet
dotnet : Имя "dotnet" не распознано как имя командлета, функции, файла сценария или выполняемой программы. Проверьт
е правильность написания имени, а также наличие и правильность пути, после чего повторите попытку.
строка:1 знак:1
- dotnet
-
+ CategoryInfo : ObjectNotFound: (dotnet:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException помогите
dotnet --info
No response
- Dominant language
- No language data
- Stars
- 7
- Forks
- 57
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/website-feedback
-
MissingOpenarea-tutorials needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
dotnet/website-feedback#1681 ·
-
idea needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 75/100
dotnet/website-feedback#1465 ·
-
area-tutorials needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
dotnet/website-feedback#1118 ·
-
mrOpenarea-tutorials spam
Difficulty 4/5 3-5 days Newbie friendliness 8/100
dotnet/website-feedback#1809 ·
-
hey jarvisOpenarea-tutorials spam
Difficulty 3/5 Half a day Newbie friendliness 8/100
dotnet/website-feedback#1808 · 1 comment ·
All issues in dotnet/website-feedback
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
aws-samples/sample-per-model-bedrock#295 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
zephyrproject-rtos/reqmgmt#177 ·
-
docs(simulation): Quickstart publishes UDP 14550, which the SITL images' own docs say not to doOpenstatus:needs-triage
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
PX4/PX4-Autopilot#29292 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
-
TSDAE's docstring implies a theta argument it does not takePossibly taken @singhharsh1708 claimed this today. Opendocumentation
Difficulty 1/5 Under an hour Newbie friendliness 74/100
SciML/PETScDiffEq.jl#282 ·
Maintainers usually reply within 1 day