-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Issues: dotnet/sdk
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
OutputPath (Issues that would be a good fit for someone new to the repository. Narrow in scope, well-defined.
-o
) option should ensure trialing slash
Area-CLI
good first issue
dotnet run
writes the "Using launch settings from ..." message to stdout instead of stderr
good first issue
Support Json format for Issues that would be a good fit for someone new to the repository. Narrow in scope, well-defined.
dotnet new list
good first issue
#43679
opened Sep 25, 2024 by
MoaidHathot
Stop inferring the Issues that would be a good fit for someone new to the repository. Narrow in scope, well-defined.
PlatformTarget
in the SDK when targeting modern .NET applications
Area-NetSDK
good first issue
Microsoft.NET.Sdk references deprecated package Microsoft.NETCore.Targets
Area-Workloads
good first issue
Issues that would be a good fit for someone new to the repository. Narrow in scope, well-defined.
Make RuntimeFrameworkVersion apply to targeting packs
Area-NetSDK
good first issue
Issues that would be a good fit for someone new to the repository. Narrow in scope, well-defined.
untriaged
Request triage from a team member
Centralize more toolsetversion-related data for tests
Area-Infrastructure
good first issue
Issues that would be a good fit for someone new to the repository. Narrow in scope, well-defined.
untriaged
Request triage from a team member
#41583
opened Jun 13, 2024 by
baronfel
Weird path added in path env
good first issue
Issues that would be a good fit for someone new to the repository. Narrow in scope, well-defined.
Infrastructure
Test Debt
dotnet tool install failed with DirectoryNotFoundException
Area-Tools
good first issue
Issues that would be a good fit for someone new to the repository. Narrow in scope, well-defined.
needs-info
dotnet command does not honor "globalPackagesFolder" in nuget.config file
Area-Tools
good first issue
Issues that would be a good fit for someone new to the repository. Narrow in scope, well-defined.
new-hire-issue
dotnet clean
(--all
?) can always fail before a build is run for apps with a RuntimeIdentifier
Area-NetSDK
good first issue
#30199
opened Jan 30, 2023 by
nagilson
dotnet workload --source looks for bad semver if you provide a faulty URL
Area-Workloads
cli-ux
Issues and PRs that deal with the UX of the CLI (exit codes, log output, verbs/options, and so on)
Cost:S
Less than 4 person weeks of work per central guidance
good first issue
Issues that would be a good fit for someone new to the repository. Narrow in scope, well-defined.
new-hire-issue
Priority:3
Work that is nice to have
#29078
opened Nov 15, 2022 by
nagilson
[API Compat] unify error message style across rules
Area-ApiCompat
good first issue
Issues that would be a good fit for someone new to the repository. Narrow in scope, well-defined.
help wanted
Issues that we would accept external contributions on. Also known as up-for-grabs.
SDK should expose available WarningLevel values as MSBuild items
Area-NetSDK
good first issue
Issues that would be a good fit for someone new to the repository. Narrow in scope, well-defined.
#24570
opened Mar 25, 2022 by
tmeschter
dotnet store
doesn't set the Framework and Runtime options as required
Area-NetSDK
good first issue
Don't copy additional files when ReferenceOutputAssembly=false for exe references
Area-NetSDK
good first issue
Issues that would be a good fit for someone new to the repository. Narrow in scope, well-defined.
Workload resolver should check for WorkloadManifest.json file instead of just looking for a directory
Area-Workloads
Cost:S
Less than 4 person weeks of work per central guidance
good first issue
Issues that would be a good fit for someone new to the repository. Narrow in scope, well-defined.
new-hire-issue
Priority:3
Work that is nice to have
NuGet.targets incorrectly performs a url-decode on filesystem paths, resulting in projects not found
good first issue
Issues that would be a good fit for someone new to the repository. Narrow in scope, well-defined.
Use 4 to 10 person weeks of work per central guidance
good first issue
Issues that would be a good fit for someone new to the repository. Narrow in scope, well-defined.
new-hire-issue
Priority:2
Work that is important, but not critical for the release
PublishUrl
as default value for PublishDir
in .NET SDK
Area-NetSDK
Cost:M
Some tests fail on Linux (CI doesn't run all tests)
Area-Infrastructure
good first issue
Issues that would be a good fit for someone new to the repository. Narrow in scope, well-defined.
File extension ".sln" is sometimes required and other times not
Area-CLI
good first issue
Issues that would be a good fit for someone new to the repository. Narrow in scope, well-defined.
NullReferenceException when running dotnet new command in Ubuntu
Area-Linux
good first issue
Issues that would be a good fit for someone new to the repository. Narrow in scope, well-defined.
dotnet sln remove flattens the solution items
good first issue
Issues that would be a good fit for someone new to the repository. Narrow in scope, well-defined.
help wanted
Issues that we would accept external contributions on. Also known as up-for-grabs.
dotnet build /v:q is not as quiet as msbuild /v:q
Cost:S
Less than 4 person weeks of work per central guidance
good first issue
Issues that would be a good fit for someone new to the repository. Narrow in scope, well-defined.
help wanted
Issues that we would accept external contributions on. Also known as up-for-grabs.
new-hire-issue
Priority:3
Work that is nice to have
Consume NuGet /embed assets group for interop type assemblies from NuGet package
Area-NetSDK
good first issue
Issues that would be a good fit for someone new to the repository. Narrow in scope, well-defined.
Previous Next
ProTip!
Follow long discussions with comments:>50.