primordic/IssueDupesLite huggingface dataset:
Repository: dotnet/diagnostics

Issue #350: [dotnet-sos] UNKNOWN items in dumpheap -stat on core file
Created: 2019-06-19T01:19:57Z
I captured a coredump of a hello-world web app using:
dotnet new web
sed -i -e 's|.UseStartup|.UseUrls("http://localhost:5000").UseStartup|' Program.cs
dotnet run
createdump --name coredump.%d 3466

But running dotnet-sos and dumpheap -stat shows several UNKNOWN items in it:
00007fe140311340       19          608 UNKNOWN
00007fe140737318       16          640 UNKNOWN
00007fe140311c08       41          984 UNKNOWN

Is this a bug? Any suggestions on how to fix this?
My complete test script and it's output is here: https://gist.github.com/omajid/76744f6635d05f677d438179014fef58
I am using a .NET Core 2.1 compiled from https://github.com/dotnet/source-build:
$ dotnet --info
.NET Core SDK (reflecting any global.json):
 Version:   2.1.507
 Commit:    e8520940d7

Runtime Environment:
 OS Name:     fedora
 OS Version:  30
 OS Platform: Linux
 RID:         fedora.30-x64
 Base Path:   /usr/lib64/dotnet/sdk/2.1.507/

Host (useful for support):
  Version: 2.1.11
  Commit:  d6a5616240

.NET Core SDKs installed:
  2.1.507 [/usr/lib64/dotnet/sdk]

.NET Core runtimes installed:
  Microsoft.NETCore.App 2.1.11 [/usr/lib64/dotnet/shared/Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

Duplicate issue #305: lldb plugin and dotnet-dump is failing to process core files on Ubuntu 18.04
Created: 2019-06-04T05:39:58Z
I'm trying to analyze core file create with dotnet-dump on Ubuntu 18.04. When I run dumpheap everything comes out as UNKNOWN:
(lldb) dumpheap
...
00007fe2d4b45548       90        53928 UNKNOWN
00007fe2d4b51a88      224        55868 UNKNOWN
00007fe2d4b50f90     1450       113654 UNKNOWN
Total 4092 objects

I also try to build current master of diagnostics and I use lldb + sosplugin + gcore -a and I get same result.
However, when I use lldb to attach to running process, everything works as expected. I can details and and I can dump particular class.
(lldb) dumpheap
…
00007fe2d4b71d00       58        42900 System.Int32[]
00007fe2d4b45548       91        54088 System.Object[]
00007fe2d4b51a88      224        55868 System.Byte[]
00007fe2d4b50f90     1450       113654 System.String
0000000001ce4e00       94       329760      Free


This is easy to repro and I'm using somewhat recent 3.0 version of dotnet.
I can share core files or provide access to my test machine.

Closing comment (2019-06-19T22:01:05Z): Your UNKNOWN types in dumpheap -stat looks like a dup of #350 which needs investigation.
Repository: dotnet/diagnostics

Issue #564: [Feature Request] Live viewer for events from event pipe
Created: 2019-10-15T21:25:47Z
Currently, there is no official tool with the functionality to view events from event pipe live. dotnet-trace only supports collecting a .nettrace file for post-mortem analysis. The most basic live viewing could just be printing events/payloads to the terminal as they come in.
@sywhang mentioned that similar functionality has been implemented previously for testing, but was never pushed to be in a supported tool.

Duplicate issue #663: Tool for tracing live events?
Created: 2019-12-03T19:24:26Z
While working on #623 and reviewing @tmds blog post about tracing .NET Core apps I've realized that we don't have any tool that would allow for tracing and viewing live events on Linux.
I can specify the list of providers to dotnet trace but I can't view the events without copying the nettrace file to Windows and opening it with PerfView. Or writing my own console line tool.
An example of a tool that works with ETW only: https://github.com/goldshtn/etrace
@noahfalk do we have any plans for a tool like this?

Closing comment (2019-12-05T11:16:00Z): @sywhang @TIHan thanks for all the information and great discussion!
I am closing the issue since it's a duplicate of #564 and #489
Repository: dotnet/diagnostics

Issue #3073: High CPU overhead monitoring AppSvcAppLogs in App Services
Created: 2022-05-16T00:54:55Z
A 1st party team reported that they see CPU usage grow by ~3.25 core-hours / hour when they enabled AppSvcAppLogs for a 3.1 .NET Core app logging ~400 ILogger messages/sec. The messages vary from 100-300 characters each. The pricing tier was P2V2 running on Linux. This CPU seems excessive and would be worth investigating. A few questions to answer:

Can we reproduce this result with another service that logs similar amounts or is there something unique here?
Has .NET Core 6.0 substantially improved perf or is it still an issue?
If it is still an issue on .NET Core 6.0, where is the overhead coming from and what are our options to improve it?

We've got a few traces privately but here is the basic idea of what is happening:

Duplicate issue #3074: High CPU overhead monitoring AppSvcAppLogs in App Services
Created: 2022-05-16T00:55:05Z
A 1st party team reported that they see CPU usage grow by ~3.25 core-hours / hour when they enabled AppSvcAppLogs for a 3.1 .NET Core app logging ~400 ILogger messages/sec. The messages vary from 100-300 characters each. The pricing tier was P2V2 running on Linux. This CPU seems excessive and would be worth investigating. A few questions to answer:

Can we reproduce this result with another service that logs similar amounts or is there something unique here?
Has .NET Core 6.0 substantially improved perf or is it still an issue?
If it is still an issue on .NET Core 6.0, where is the overhead coming from and what are our options to improve it?

We've got a few traces privately but here is the basic idea of what is happening:

Closing comment (2022-05-16T11:14:18Z): @noahfalk it's the same as #3073
By accident or intention?
Repository: dotnet/diagnostics

Issue #2206: dotnet-gcdump and dotnet-trace single-file deployments regressed in last release
Created: 2021-04-22T19:46:36Z
Description
Im trying to run dotnet-trace and dotnet-gcdump in an alpine container. Have downloaded the musl-x64 versions, apk-added curl and icu, done chmod+x on the downloaded binary, and when i run either of them i get the following error:
Error:
An assembly specified in the application dependencies manifest (dotnet-trace.deps.json) was not found:
package: 'Microsoft.Diagnostics.Tracing.TraceEvent', version: '2.0.64'
path: 'lib/netstandard2.0/Dia2Lib.dll'
Note that dotnet-dump worked just fine - both collect and analyze.

Configuration
Alpine-3.1-amd64
.net core 3.1.12
latest download of musl binaries for dotnet-trace and dotnet-dump
running the container in AKS

dotnet-info output
Host (useful for support):
Version: 3.1.12
Commit:  0267ad09c6
.NET Core SDKs installed:
No SDKs were found.
.NET Core runtimes installed:
Microsoft.AspNetCore.App 3.1.12 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 3.1.12 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Regression?
Possibly. I was able to do dotnet-gcdump in a similar container (alpine-3.1, amd64, .net core 3.1.12) running on ACI, on 3/22/2021.
I haven't tried again in ACI since ACI vs. AKS shouldn't really matter at all here.

Other information
I will be trying with the two older releases from the github releases links in the next few hours and post an update here in case that works.
I see a workaround for this issue: microsoft/perfview#1002 in this file: https://github.com/dotnet/diagnostics/blob/release/stable/src/Tools/Directory.Build.targets

Duplicate issue #2227: dotnet-trace - "An assembly specified in the application dependencies manifest was not found"
Created: 2021-04-28T14:47:46Z
Description


Download a standalone (x64, for Linux or Windows) version of dotnet-trace from the official download page


Run the downloaded file


See the error
PS C:\> dotnet-trace
Error:
An assembly specified in the application dependencies manifest (dotnet-trace.deps.json) was not found:
package: 'Microsoft.Diagnostics.Tracing.TraceEvent', version: '2.0.64'
path: 'lib/netstandard2.0/Dia2Lib.dll'



Install the dotnet-trace through the dotnet tool, (the version 5.0.221401 is downloaded)


The binaries, downloaded by the dotnet tool, work fine


Configuration
The issue reproduces for x64 binaries both for Linux and for Windows 10.

Closing comment (2021-04-28T18:06:11Z): Dupe of #2206
Repository: dotnet/diagnostics

Issue #344: dotnet tools are hard to deploy into production environments
Created: 2019-06-17T23:17:53Z
Our current deployment story uses dotnet tool install, but this is hard to use on production machines because the SDK typically isn't installed. Similarly NuGet is unlikely to be installed. We need to provide alternate deployment options that are more suited for production environments. A few possibilities we discussed in the past:

Make a self-contained tool that is downloadable via a direct link from Microsoft download center
Make container images that have the tools preinstalled
Put some version of the tool in-box with the runtime
Put a minimal tool downloader (ie dotnet tool install) in-box with the runtime.

My guess is that option (1) will be the easiest in the short term and is reasonably general purpose. If feedback after doing (1) says it still isn't sufficient we could then investigate if we should do any of 2/3/4 in addition.

Duplicate issue #1524: Tools can't run without the SDK on a production server?!
Created: 2020-09-03T17:01:23Z
People don't and shouldn't have SDKs installed on a PROD server. However tools used for diagnostics should be able to be run even without disturbing the environment. Any plans to release these tools as they should ie packages that can be run with just the runtime installed?

Closing comment (2020-09-04T10:16:52Z): There is a pre-existing issue covering this. I'm going to close this one as duplicate and progress on this problem can be tracked in #344
Repository: dotnet/docs

Issue #3623: Fix Link to Sample Application in Microsoft Document
Created: 2017-11-06T20:55:00Z
Fix Link to Sample Application in Microsoft Document
Regarding this document - https://docs.microsoft.com/en-us/dotnet/framework/wpf/advanced/how-to-localize-an-application
in above document , in Create a Sample Application section
Link to LocBaml Tool Sample does not work
edit by @mairaw: added docs info below

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 72e544a8-3979-26ea-39fb-316eafa71cdb
Version Independent ID: 5b84e3b3-e09f-be5d-8936-ed1ceb81203c
Content: How to: Localize an Application
Content Source: docs/framework/wpf/advanced/how-to-localize-an-application.md
Service: unspecified
Product: dotnet-framework
GitHub Login: @dotnet-bot
Microsoft Alias: dotnetcontent

Duplicate issue #5892: Link to LocBaml tool is dead.
Created: 2018-06-10T08:58:24Z
Is there anyway to obtain LocBaml tool ?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 4baeeb7d-bba4-c8c5-6f54-97dc68a59aef
Version Independent ID: d248598d-5657-1a8c-3f91-b37384243eff
Content: WPF Globalization and Localization Overview
Content Source: docs/framework/wpf/advanced/wpf-globalization-and-localization-overview.md
Product: dotnet-framework
GitHub Login: @dotnet-bot
Microsoft Alias: dotnetcontent

Closing comment (2018-06-19T07:16:45Z): Duplicate of #3623
Repository: dotnet/docs

Issue #16943: Missing C# compiler warnings
Created: 2020-02-03T17:36:54Z
id: CS1998
title: Async method lacks 'await' operators and will run synchronously
id: CS8600
title: Converting null literal or possible null value to non-nullable type.
id: CS8601
title: Possible null reference assignment.
id: CS8602
title: Dereference of a possibly null reference.
id: CS8604
title: Possible null reference argument.
id: CS8610
title: Nullability of reference types in type of parameter doesn't match overridden member.
id: CS8611
title: Nullability of reference types in type of parameter doesn't match partial method declaration.
id: CS8613
title: Nullability of reference types in return type doesn't match implicitly implemented member.
id: CS8618
title: Non-nullable field is uninitialized. Consider declaring as nullable.
id: CS8619
title: Nullability of reference types in value doesn't match target type.
id: CS8621
title: Nullability of reference types in return type doesn't match the target delegate.
id: CS8622
title: Nullability of reference types in type of parameter doesn't match the target delegate.
id: CS8625
title: Cannot convert null literal to non-nullable reference type.
id: CS8632
title: The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
id: CS8634
title: The type cannot be used as type parameter in the generic type or method. Nullability of type argument doesn't match 'class' constraint.
id: CS8655
title: The switch expression does not handle some null inputs.
id: CS8667
title: Partial method declarations have inconsistent nullability in constraints for type parameter
id: CS8670
title: Object or collection initializer implicitly dereferences possibly null member.
id: CS8714
title: The type cannot be used as type parameter in the generic type or method. Nullability of type argument doesn't match 'notnull' constraint.
id: CS8762
title: Parameter may not have a null value when exiting in some condition.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: fc586192-534e-0108-d265-c4f2f6947c57
Version Independent ID: 4d39f536-5d78-335b-3525-d4b581c28fdc
Content: C# Compiler Errors
Content Source: docs/csharp/language-reference/compiler-messages/index.md
Product: dotnet-csharp
Technology: csharp-diagnostics
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Duplicate issue #16955: Missing C# compiler warning CS8625
Created: 2020-02-03T17:43:06Z
id: CS8625
title: Cannot convert null literal to non-nullable reference type.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: fc586192-534e-0108-d265-c4f2f6947c57
Version Independent ID: 4d39f536-5d78-335b-3525-d4b581c28fdc
Content: C# Compiler Errors
Content Source: docs/csharp/language-reference/compiler-messages/index.md
Product: dotnet-csharp
Technology: csharp-diagnostics
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Closing comment (2020-03-09T15:31:24Z): Duplicate of #16943
Repository: dotnet/docs

Issue #32949: dotnet install command. 
Created: 2022-12-08T14:34:45Z
From this documentation page, dotnet new install does not seem to work on 6.0.111, But I noticed that the new format was able to work for me using the dotnet new --install stated in the docs here
Current dotnet versions. System is MacOS
.NET SDKs:
Version      Status
----------------------------------------
6.0.111      Up to date.
6.0.202      Patch 6.0.203 is available.

Try out the newest .NET SDK features with .NET 7.0.100.

.NET Runtimes:
Name                          Version      Status
---------------------------------------------------------------------
Microsoft.NETCore.App         6.0.1        Patch 6.0.11 is available.
Microsoft.AspNetCore.App      6.0.4        Patch 6.0.11 is available.
Microsoft.NETCore.App         6.0.4        Patch 6.0.11 is available.
Microsoft.AspNetCore.App      6.0.11       Up to date.
Microsoft.NETCore.App         6.0.11       Up to date.



Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 097102bb-f6d9-c469-5556-ae1f16fdc4fe
Version Independent ID: 77b25381-6e0f-949f-5f96-b83e9b61e9fc
Content: Create a project template for dotnet new - .NET
Content Source: docs/core/tutorials/cli-templates-create-project-template.md
Product: dotnet-fundamentals
GitHub Login: @adegeo
Microsoft Alias: adegeo


Associated WorkItem - 52198

Duplicate issue #32958: -- is missing for install
Created: 2022-12-08T21:21:13Z
[Enter feedback here]
the command should be dotnet new --install ./
otherwise it wont work!

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 097102bb-f6d9-c469-5556-ae1f16fdc4fe
Version Independent ID: 77b25381-6e0f-949f-5f96-b83e9b61e9fc
Content: Create a project template for dotnet new - .NET
Content Source: docs/core/tutorials/cli-templates-create-project-template.md
Product: dotnet-fundamentals
GitHub Login: @adegeo
Microsoft Alias: adegeo

Closing comment (2022-12-27T19:57:25Z): Duplicate of #32949
Repository: dotnet/docs

Issue #25296: Update required for VS 2019
Created: 2021-07-22T10:21:49Z
All the information detailed here is not available or visible in VS2019. To add a service using a wsdl defintion you cannot performed this through Connected Services as the OpenAPI does not support the operation.
As for Add Service Reference tool. this is buggy, sometimes it works other times it does not, currently not working VS 2019 Pro Version 16.10.3

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0e89651a-5ad9-c3f9-146f-8d87b87d9e11
Version Independent ID: 85c0e55f-abc0-3b2d-409a-06042b1f3ebb
Content: Add WCF Web Service Reference - .NET
Content Source: docs/core/additional-tools/wcf-web-service-reference-guide.md
Product: dotnet-fundamentals
GitHub Login: @dasetser
Microsoft Alias: dotnetcontent

Duplicate issue #26280: No install instructions
Created: 2021-09-27T17:29:25Z
A key part of instructions on using a tool would be how to install the tool.  Where to find it, how to get it installed.  I can't find it in the VS marketplace, searching in VS Extensions dialog brings nothing, and I can't find any instructions anywhere on how to get the extension into VS 2019.  How about adding some guidance for this?
When I try to add a service reference to my project, I get lots of options, but none are WCF related.


Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0e89651a-5ad9-c3f9-146f-8d87b87d9e11
Version Independent ID: 85c0e55f-abc0-3b2d-409a-06042b1f3ebb
Content: Add WCF Web Service Reference - .NET
Content Source: docs/core/additional-tools/wcf-web-service-reference-guide.md
Product: dotnet-fundamentals
GitHub Login: @dasetser
Microsoft Alias: dotnetcontent

Closing comment (2022-02-10T22:17:51Z): Related to #25296.
Repository: dotnet/docs

Issue #8769: What exactly the Cluster result is displaying
Created: 2018-10-31T05:16:22Z
Hi when we run the program every time we get the different Cluster ID ,Is the Cluster ID 1 means Iris-setosa ,ID 2 means Iris-versicolor, and ID 3 means Iris-virginica ,But we can see that as the Input is related to Iris-setosa in the program but in out put the result is as Cluster: 2 ,Can you kindly help me to clear about what exactly is for ClusterID and also the score result distance means what exactly the Score output is used for ,In Regression model we get the clear output,In Clustering how can we find which exact output.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 925c8fe9-ba0b-bd2c-cea0-9d851ece8825
Version Independent ID: 41cafff5-6418-2e54-3a0d-ee29fb1fca1f
Content: Use ML.NET to cluster iris flowers (clustering)
Content Source: docs/machine-learning/tutorials/iris-clustering.md
Product: dotnet-ml
GitHub Login: @pkulikov
Microsoft Alias: johalex

Duplicate issue #8768: What is Clustering ID in output exactly means
Created: 2018-10-31T04:55:52Z
Hi when we run the program every time we get the different Cluster ID ,Is the Cluster ID 1 means Iris-setosa ,ID 2 means Iris-versicolor, and ID 3 means Iris-virginica ,But we can see that as the Input is related to Iris-setosa in the program but in out put the result is as Cluster: 2 ,Can you kindly help me to clear about what exactly is for ClusterID and also the score result distance means what exactly the Score output is used for ,In Regression model we get the clear output,In Clustering how can we find which exact output.

Closing comment (2018-10-31T07:24:22Z): Duplicate of #8769
Repository: dotnet/docs

Issue #4831: .NET Compiler Platform SDK Tutorial: Build your first analyzer.
Created: 2018-03-30T20:44:39Z
@BillWagner commented on Mon Jul 17 2017
This should be as simple as possible. if without brackets might be good.
Add unit tests for test cases for code.

@MaStr11 commented on Tue Mar 27 2018
These articles might be a good source for this
Roslyn Wiki How To Write a C# Analyzer and Code Fix
MSDN C# and Visual Basic - Use Roslyn to Write a Live Code Analyzer for Your API

Duplicate issue #5073: How to create an analyzer
Created: 2018-04-29T15:29:24Z
Can you add a link to a document that explains how to create an analyzer from scratch? Would be nice :) Thanks!

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ee024463-2572-2106-a85d-7c53f8d9dc0c
Version Independent ID: 1cd4a2f3-3055-1faa-0fa9-46bbfb6dcef1
Content: The Roslyn based Analyzers - .NET
Content Source: docs/standard/analyzers/index.md
Service: unspecified
GitHub Login: @BillWagner
Microsoft Alias: billwagner

Closing comment (2018-04-30T22:25:40Z): Duplicate of #4831
Repository: dotnet/docs

Issue #18900: Code example not compliant with guideline
Created: 2020-06-11T07:48:27Z
Page says:

Do not use implicit typing to determine the type of the loop variable in foreach loops.
The following example uses explicit typing in a foreach statement.
foreach (var ch in laugh)
{
   if (ch == 'h')
...


The first line of the code example should read foreach (char ch in laugh) according to the guideline text right above it.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 5a3c147e-2271-4d7c-712b-2f705b5ecbc5
Version Independent ID: 2c1a7cfe-364e-408e-77c1-9fae2b0da643
Content: C# Coding Conventions - C# Programming Guide
Content Source: docs/csharp/programming-guide/inside-a-program/coding-conventions.md
Product: dotnet-csharp
Technology: csharp-get-started
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Duplicate issue #18940: Implicitly Typed Local Variables
Created: 2020-06-13T07:22:28Z
In the section Implicitly Typed Local Variables, it is recommended to not to use implicit typing to determine the type of the loop variable in foreach loops.
But in the example, implicit typing is used (var - implicit, char - explicit).
Should it be (char ch in laugh) instead of (var ch in laugh)?
The following example uses explicit typing in a foreach statement.
foreach (var ch in laugh)
{
    if (ch == 'h')
        Console.Write("H");
    else
        Console.Write(ch);
}
Console.WriteLine();

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 5a3c147e-2271-4d7c-712b-2f705b5ecbc5
Version Independent ID: 2c1a7cfe-364e-408e-77c1-9fae2b0da643
Content: C# Coding Conventions - C# Programming Guide
Content Source: docs/csharp/programming-guide/inside-a-program/coding-conventions.md
Product: dotnet-csharp
Technology: csharp-get-started
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Closing comment (2020-06-19T13:49:16Z): closing as a duplicate of #18900
Repository: dotnet/docs

Issue #35480: [Breaking change]: .NET SDK 8.0.100 will require Visual Studio and MSBuild version 17.7
Created: 2023-05-24T17:11:10Z
Description
Per the published support rules, we update the minimum VS/MSBuild version for each new major release with a one quarter delay. For the GA release, 8.0.100 will require 17.7 to be loaded but only support targeting 7.0 in that version. To target net8.0, customers will have to use 17.8 or newer.
https://learn.microsoft.com/en-us/dotnet/core/porting/versioning-sdk-msbuild-vs#targeting-and-support-rules
Version
.NET 8 RC 1
Previous behavior
.NET 8.0.1xx-preview1 required 17.4. This was updated to 17.6 in preview4.
See https://learn.microsoft.com/en-us/dotnet/core/compatibility/sdk/7.0/vs-msbuild-version
New behavior
Starting in RC1, 8.0.1xx will require 17.7 MSBuild/VS versions.
Type of breaking change

 Binary incompatible: Existing binaries may encounter a breaking change in behavior, such as failure to load or execute, and if so, require recompilation.
 Source incompatible: When recompiled using the new SDK or component or to target the new runtime, existing source code may require source changes to compile successfully.
 Behavioral change: Existing binaries may behave differently at run time.

Reason for change
This is our standard support policy for the SDK as we can't support all prior versions of MSBuild/VS.
Recommended action
Upgrade the version of Visual Studio being used.
Feature area
SDK
Affected APIs
No response

Associated WorkItem - 118227

Duplicate issue #36659: [Breaking change]: .NET 8.0.100 SDK requires MSBuild 17.7 to load and 17.8 to target net8.0
Created: 2023-08-11T20:07:47Z
Description
We've updated the minimum required MSBuild and Visual Studio version for the 8.0.100-rc.1 SDK to be 17.7.
Change to the minimum
dotnet/sdk#34565
Other document with this information
https://learn.microsoft.com/en-us/dotnet/core/porting/versioning-sdk-msbuild-vs#targeting-and-support-rules
Prior breaking change notice
https://learn.microsoft.com/en-us/dotnet/core/compatibility/sdk/7.0/vs-msbuild-version
Version
.NET 8 RC 1
Previous behavior
Prior previews would load into 17.6 (though the preview 7 SDK would error when used with 17.6).
New behavior
The .NET 8.0.100-rc.1 SDK will not even load in 17.6 or earlier VS.
Type of breaking change

 Binary incompatible: Existing binaries may encounter a breaking change in behavior, such as failure to load or execute, and if so, require recompilation.
 Source incompatible: When recompiled using the new SDK or component or to target the new runtime, existing source code may require source changes to compile successfully.
 Behavioral change: Existing binaries may behave differently at run time.

Reason for change
Planned minimum version update
Recommended action
Customers should update their version of Visual Studio to 17.7.0 or newer or use global.json to pin to an older SDK.
Feature area
SDK
Affected APIs
No response

Closing comment (2023-09-05T20:42:39Z): @marcpopMSFT This looks like a duplicate of #35480?
Repository: dotnet/docs

Issue #27438: No help page for C# error CS7036
Created: 2021-12-07T18:54:27Z
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: bbb051ee-f020-66ba-c601-4a08ad32ef61
Version Independent ID: 58a19505-ac46-c5c8-12cc-fe87b6aa18a7
Content: Sorry, we don't have specifics on this C# error
Content Source: docs/csharp/misc/sorry-we-don-t-have-specifics-on-this-csharp-error.md
Product: dotnet-csharp
Technology: csharp-diagnostics
GitHub Login: @BillWagner
Microsoft Alias: wiwagn


Associated WorkItem - 189693

Duplicate issue #36942: OK, what about an error description for CS7036
Created: 2023-09-01T07:20:30Z
[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: bbb051ee-f020-66ba-c601-4a08ad32ef61
Version Independent ID: 58a19505-ac46-c5c8-12cc-fe87b6aa18a7
Content: Sorry, we don't have specifics on this C# error
Content Source: docs/csharp/misc/sorry-we-don-t-have-specifics-on-this-csharp-error.md
Product: dotnet-csharp
Technology: csharp-diagnostics
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Closing comment (2023-09-05T13:37:14Z): Duplicate of #27438
Repository: dotnet/docs

Issue #31178: Inconsistent naming for the IP EndPoint
Created: 2022-09-14T18:00:31Z
The snippet included from IPEndpoint names the endpoint ipEndpoint, but the client and server code which follows each expect a variable named simply endPoint.
I would have edited, but it was not clear to me how to edit the included Program.cs files (or if that would have broken something else even if I did know how).

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 8918b064-85a6-4644-ecf7-aac48386c58d
Version Independent ID: 7f7bab6f-3aa6-8755-a541-a6c3b0121f1c
Content: Use Sockets to send and receive data - .NET
Content Source: docs/fundamentals/networking/sockets/socket-services.md
Product: dotnet-fundamentals
GitHub Login: @IEvangelist
Microsoft Alias: dapine

Duplicate issue #31147: Bug in example code
Created: 2022-09-14T10:14:10Z
"ipEndPoint" becomes "endPoint".

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 8918b064-85a6-4644-ecf7-aac48386c58d
Version Independent ID: 7f7bab6f-3aa6-8755-a541-a6c3b0121f1c
Content: Use Sockets to send and receive data - .NET
Content Source: docs/fundamentals/networking/sockets/socket-services.md
Product: dotnet-fundamentals
GitHub Login: @IEvangelist
Microsoft Alias: dapine

Closing comment (2022-09-15T13:51:12Z): Related to #31178
Repository: dotnet/dotnet-docker

Issue #1374: Images based on Alpine 3.9 don't pass vulnerability scanner
Created: 2019-10-07T22:36:51Z
Steps to reproduce the issue

Running docker image vulnerability scanners (in our case Clair from coreos) on mcr.microsoft.com/dotnet/core/runtime-deps:3.0-alpine produces vulnerability warnings for CVE-2019-14697.

Expected behavior
Latest asp.net core docker images should ideally remain patched and not report vulnerabilities if possible.  Obviously the .net core images are dependent on their base official images.  In this case it seems Alpine has addressed the vulnerability but did so in a minor version instead of a patch to 3.9 (See alpinelinux/docker-alpine#34).
If I understand the .net core tagging scheme, this means that mcr.microsoft.com/dotnet/core/runtime-deps:3.0-alpine will not automatically be patched, and that users will need to opt in to use an mcr.microsoft.com/dotnet/core/runtime-deps:3.0-alpine3.10 image instead.  Is that correct?
I see that an alpine 3.10 based version is available in the nightly builds, is there an ETA for this image to be published in the official repo?
From what I can tell, it seems the alpine 3.10 image has been available for a couple of months (even though .net core 3.0 images were just barely released).  Since it seems they fix vulnerabilities in minor version updates (instead of patches), what is the expected time-frame in which we can expect official .net core images to adopt new OS minor versions?  Those of us in enterprise/corporate environments need to be able to build on .net core and still satisfy compliance policies.  Our organization is still early in our adoption of .net core on docker and trying to put together our security policies, so forgive me if I'm misunderstanding the landscape and my expectations are unreasonable.
Thanks for any help or info you can provide!

Duplicate issue #1379: CVE-2019-14697 on image: mcr.microsoft.com/dotnet/core/aspnet:2.2-alpine3.9
Created: 2019-10-09T16:01:29Z
Steps to reproduce the issue
On image scan i found that the image contains package musl:1.1.20-r4 which has CVE-2019-14697
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14697
This is fixed in musl version: 1.1.20-r5
Expected behavior
No security issues
Actual behavior
Having https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14697

Closing comment (2019-10-09T18:15:43Z): This is a duplicate of #1374.
Repository: dotnet/dotnet-docker

Issue #940: Provide Documentation on Securing ASP.NET Core Containers
Created: 2019-02-25T12:45:00Z
I've discovered that you can run an ASP.NET Core image with a read-only file system but this requires you to turn off debugging and profiling support because otherwise you get an error. Full sample here.
docker run --rm --read-only -it -p 8000:80 -e COMPlus_EnableDiagnostics=0 my-asp-app

There are also a myriad of settings we can use in Kubernetes. Here is a sample Pod yaml:
apiVersion: v1
kind: Pod
metadata:
  name: security-context-demo
spec:
  securityContext:
    runAsUser: 1000
    fsGroup: 2000
  volumes:
  - name: sec-ctx-vol
    emptyDir: {}
  containers:
  - name: sec-ctx-demo
    image: gcr.io/google-samples/node-hello:1.0
    volumeMounts:
    - name: sec-ctx-vol
      mountPath: /data/demo
    securityContext:
      allowPrivilegeEscalation: false
      readOnlyRootFilesystem: true
      capabilities:
        add: ["NET_ADMIN", "SYS_TIME"]


allowPrivilegeEscalation - Stops escalation of privlieges to super user.
readOnlyRootFilesystem - Enables the read-only file system I talk about above.
runAsUser - Run as a different user.
fsGroup - Run as a different group.
capabilities - Limit the linux capabilities available to the app.

As a linux noob, I'd really like more information and guidance on runAsUser, fsGroup and capabilities in particular. It would be ideal if a basic set of capabilities could be provided to get a hello world app running but also some description of what needs to be added to get additional features.

Duplicate issue #4746: Make Kubernetes sample with r/o file system
Created: 2023-07-12T17:46:44Z
It is one of the Security Context options.
https://kubernetes.io/docs/tasks/configure-pod-container/security-context/

Closing comment (2023-07-19T18:53:23Z): [Triage]
Related to #940
Repository: dotnet/dotnet-docker

Issue #4300: Consider defining a helper "health check" utility for distroless scenarios
Created: 2023-01-05T20:48:53Z
The use of the HEALTHCHECK instruction often involves the use of a command that executes an HTTP request to the application in order to verify its health. That command might be curl or wget for Linux containers. This becomes problematic for distroless/chiseled containers that would likely want to exclude such commands. How then would a call be made to verify the health of the app?
One solution is to include a basic .NET application that execute the HTTP request (see #4296). Depending on the ubiquity of such a solution, it might make sense for .NET to provide its own implementation of this application that can be easily injected into .NET distroless/chiseled solutions.
I'll illustrate this with an example. Let's say .NET publishes an httpclient image that contains a .NET app which simply sends an HTTP request to a URL provided as an argument. It returns 0 if the request succeeds and 1 if it fails. A distroless implementation could consume this app like the following:
# Build stage excluded for brevity
...

FROM mcr.microsoft.com/dotnet/nightly/runtime-deps:7.0-jammy-chiseled
WORKDIR /app
COPY --from=build /app .

# Inject the .NET httpclient into the image to use for the health check
COPY --from=mcr.microsoft.com/dotnet/httpclient:7.0 /httpclient.exe /
HEALTHCHECK CMD [ "/httpclient.exe", "http://localhost/healthz" ]

ENTRYPOINT ["./app"]
I think it'd be important to understand the landscape of how customers are using health checks to determine the suitability of a pre-defined tool like this. We obviously don't want to be reimplementing curl in .NET but allowing for a little bit of behavior customization in order to fulfill a large portion of customer scenarios seems reasonable.

Duplicate issue #4323: Provide documentation for HEALTHCHECK scenarios in distroless environments
Created: 2023-01-11T19:18:09Z
This is related to #4300 and specifically the comment to provide documentation for HEALTHCHECK scenarios in distroless. This would help guide customers for authoring their own .NET application that can be used as the executable for a HEALTHCHECK in a distroless environment.

Closing comment (2025-01-06T19:42:21Z): Closing as duplicate of #4300
Repository: dotnet/dotnet-docker

Issue #4117: Proposal: New tagging pattern for .NET 8 previews
Created: 2022-10-04T17:27:39Z
New tagging pattern for .NET 8 previews
Problem Description
The .NET tagging pattern has historically used a floating major/minor version tag (e.g. 7.0) for each release, starting with preview releases. We'll focus on .NET 7 as the basis for discussion here. With the release of .NET 7 Preview 1 we published 7.0 and 7.0.0-preview.1 tags. Customers were free to use the floating 7.0 tag to move along with each preview or explicitly transition between each preview release by using the tag specific to the preview number (e.g. 7.0.0-preview.1).
The intent with this pattern was to allow early adopters to start using the new features of preview releases and seamlessly transition to supported releases once the version had its GA release. The floating 7.0 tag would give you the latest preview versions as they were being released and then transition to supported servicing releases after GA of .NET 7.
This has lead to some confusion because the 7.0 tag doesn't indicate its supported state at all (see #3531). It has caused some automation tools that to mistakenly think your Dockerfile isn't referencing the latest version of .NET if it's referencing a 6.0 tag (currently the latest supported release). We'd like to avoid this confusion in our tagging pattern.
Proposal
Beginning with .NET 8, the .NET container images will adopt a new tagging pattern that helps to indicate the supported state of the tag. The primary difference from the tagging pattern used historically is that a floating 8.0 won't be introduced until later in the release cycle. Instead, a floating 8.0-preview tag will be used. The tagging pattern maps to the timeline of the .NET 8 release cycle, shown below. For purposes of brevity, tags specific to patch versions and OS (e.g. 8.0.0-preview, 8.0-preview-alpine) aren't shown here.



Release
New Tags
Updated Tags




.NET 8 Preview 1
8.0-preview8.0.0-preview.1
n/a


.NET 8 Preview N(where N > 1)
8.0.0-preview.N
8.0-preview


.NET 8 RC 1
8.08.0.0-rc.1
n/a


.NET 8 RC N(where N > 1)
8.0.0-rc.N
8.0


.NET 8 GA
n/a
8.0



With each preview release, the 8.0-preview tag will be updated to reference the latest preview image. That will continue until the first RC release. At that point, the 8.0 tag will be introduced and maintenance of the 8.0-preview tag will be discontinued. Since the RC release will be supported for production use, the intent here is to make this transition now, ahead of the GA release, to provide a smooth experience starting from now, through GA, and into servicing.
We believe this tagging pattern is a good compromise that allows tag changes to be made well ahead of the GA release and yet doesn't mislead people into thinking a .NET version is ready for production use when it's still in preview.

Duplicate issue #4197: Add Dockerfiles for .NET 8
Created: 2022-11-08T21:28:48Z
There are early builds of .NET 8 that we should be able to target in the Dockerfiles.

Closing comment (2022-11-08T21:57:22Z): Related to #4117
Repository: dotnet/dotnet-docker

Issue #1573: Validate release artifacts
Created: 2020-01-13T20:13:00Z
Validate that images being published contain a .NET version that match the latest .NET versions (2.x, 3.x) defined by the releases-index.  This ensures that an image being published wasn't somehow misconfigured to contain an older version of .NET.

Duplicate issue #2166: Unit tests to validate installed .NET version
Created: 2020-08-12T13:04:31Z
In order to prevent issues like #2163 from occurring, we should consider having unit tests that validate each image contains the expected version of .NET runtime, ASP.NET Core, or SDK installed.  The expected versions are contained in the https://github.com/dotnet/dotnet-docker/blob/master/manifest.versions.json file.

Closing comment (2023-04-19T18:44:43Z): [Triage]
Closing as a duplicate of #1573
Repository: dotnet/dotnet-docker

Issue #2275: Include sample Dockerfiles for Windows Server Core
Created: 2020-09-29T15:19:07Z
With the introduction of Windows Server Core images with #1852, there should be sample Dockerfiles based on Server Core once there are official images so that the community can see examples of apps based on Server Core in addition to Nano Server.
Currently, the sample tests explicitly exclude Server Core which will need to be enabled once these images are made available: see #2274 (comment).

Duplicate issue #2424: Sample Dockerfiles should exist that demonstrate how to use the new Windows Server Core images
Created: 2020-12-01T13:54:18Z
With the introduction of Windows Server Core based images in 5.0, new windowsservercore Dockerfiles should be added to the samples that illustrate how to best use the images.

Closing comment (2020-12-02T13:47:32Z): This is a duplicate of #2275 which was mistakenly closed.  I'll re-open it.
Repository: dotnet/maui

Issue #14506: [iOS/Catalyst] CollectionView VisualDiagnostic Item Registration is broken
Created: 2023-04-11T08:18:11Z
Description

When a CollectionView ItemsSource is populated, UI Items are generated and registered in VisualDiagnostics. On iOS and Mac Catalyst, the first item in the given ItemSource is added to multiple items. The underlying UICollectionView is not creating it, but it does appear in LogicalChildren and IVisualTreeElement.Children as Virtual items. These views also appear in the Live Visual Tree and are being registered with OnChildAdd.
I could only reproduce this on iOS and Catalyst.
Steps to Reproduce
Run my reproduction project: https://github.com/drasticactions/MauiRepros/tree/main/MauiCollectionView
Link to public reproduction project repository
https://github.com/drasticactions/MauiRepros/tree/main/MauiCollectionView
Version with bug
7.0 (current)
Last version that worked well
7.0 (current)
Affected platforms
iOS, macOS
Affected platform versions
All versions
Did you find any workaround?
No response
Relevant log output
No response

Duplicate issue #18517: [iOS] CollectionView has more logical children than items (potential memory leak)
Created: 2023-11-03T20:10:04Z
Description
On iOS, CollectionView ends up having more logical children than items. For instance, if you have 2 items and a Label as Item Template, and inspect the LogicalChildren, it ends up with 3 labels instead of 2. This third label is not visible on the app.
This works as expected on Android and Windows.
Some more details:
_measurementCells is caching the cells that were bound so they can be reused, but those are cleared up while loading and not the ItemView children. Next time a cell is analyzed it is re-bound, so in the sample the first item is added twice.

https://github.com/dotnet/maui/blob/main/src/Controls/src/Core/Handlers/Items/iOS/ItemsViewController.cs#L295
https://github.com/dotnet/maui/blob/main/src/Controls/src/Core/Handlers/Items/iOS/ItemsViewController.cs#L352

Steps to Reproduce
Run the CollectionViewItemsWithFixedWidthAndDifferentHeight Core.DeviceTests for iOS.
Link to public reproduction project repository

  
    
      maui/src/Controls/tests/DeviceTests/Elements/CollectionView/CollectionViewTests.cs
    
    
         Line 237
      in
      340fc25
    
  
  
    

        
          
           public async Task CollectionViewItemsWithFixedWidthAndDifferentHeight()  
        
    
  


Version with bug
8.0.0-rc.2.9511
Is this a regression from previous behavior?
Not sure, did not test other versions
Last version that worked well
Unknown/Other
Affected platforms
iOS
Affected platform versions
No response
Did you find any workaround?
No response
Relevant log output
No response

Closing comment (2023-11-04T04:40:58Z): Could be related to #14506
Repository: dotnet/maui

Issue #9578: Different SplashScreen for Light and Dark Modes
Created: 2022-08-22T12:52:46Z
Description
Hi,
It will be great if we will be able to set a different ResourceDictionary for the Splash Screen when light and Dark..
Public API Changes
#if AppTheme is Light
<MauiSplashScreen Include="Resources\Splash\splash_light.svg" Color="#FFFFFF" BaseSize="128,128" />

#if AppTheme is Dark
<MauiSplashScreen Include="Resources\Splash\splash_dark.svg" Color="#000000" BaseSize="128,128" />


Intended Use-Case
To set the AppTheme's Splash Screen

Duplicate issue #12944: MAUI_splashscreen: How to set Splash screen for Light and Dark mode for iOS and Android
Created: 2023-01-26T17:19:28Z
Description
Can someone please guide details with snippet on how to set Splash screen for Light and Dark mode for iOS and Android as we are migrating from Xamarin Forms to MAUI and I am not able to find documentation mentioning details for both mode. The documentation we are referring currently is at this link "https://learn.microsoft.com/en-us/dotnet/maui/user-interface/images/splashscreen?view=net-maui-7.0&tabs=android"
Thanks.
Steps to Reproduce
Splash screen for Light and Dark mode for iOS and Android.
Link to public reproduction project repository
https://learn.microsoft.com/en-us/dotnet/maui/user-interface/images/splashscreen?view=net-maui-7.0&tabs=android
Version with bug
7.0 (current)
Last version that worked well
7.0 (current)
Affected platforms
iOS, Android
Affected platform versions
iOS, Android
Did you find any workaround?
No response
Relevant log output
No response

Closing comment (2024-08-12T08:14:09Z): Duplicate of #9578
Repository: dotnet/maui

Issue #6412: Vertical Scrolling is hard/Practically unusable for a CollectionView inside a CarouselView
Created: 2022-04-22T14:32:56Z
Description
xamarin/XamarinCommunityToolkit#591
The above issue is the usecase for this.
When a collectionview is scrolled inside CarouselView , collectionview does not scroll but the CarouselView's Position gets changed. If there is a slight slant to the users swipe, the carouselview is scrolled instead of the collectionview. In short scrolling a collectionview inside a CarouselView is hard for the user to do.
Steps to Reproduce

Create CarouselView
Add a collectionview inside it
Try to scroll

Version with bug
Release Candidate 1 (current)
Last version that worked well
Unknown/Other
Affected platforms
Android
Affected platform versions
Android 10, 11, 12
Did you find any workaround?
No, The Issue seems to be with CollectionView or the CarouselView Implementation
Relevant log output
No response

Duplicate issue #6707: Vertical CollectionView should not attempt to scroll horizontally
Created: 2022-04-30T17:00:22Z
Description
Even though CollectionView has vertical orientation, it still attempts to scroll horizontally. It makes CollectionView very user-unfriendly, as you need to move your finger exactly vertical, otherwise you cannot scroll it.
Repro project: https://github.com/Dreamescaper/maui-6707-repro
Steps to Reproduce

Run repro project.
Try to scroll the list, moving the finger at some angle (e.g. ~45°).

ER:
CollectionView is scrolled down.
AR:
CollectionView is not scrolled down, horizontal scroll animation is present instead.

Version with bug
Release Candidate 2 (current)
Last version that worked well
Unknown/Other
Affected platforms
Android
Affected platform versions
Android 12
Did you find any workaround?
No response
Relevant log output
No response

Closing comment (2022-04-30T17:05:19Z): This issue is similar to #6412, but for the case with root CollectionView.
Issue #6412 is present on Xamarin.Forms as well, this one - only on MAUI.
Repository: dotnet/maui

Issue #21681: HideSoftInputOnTapped only works when ContentPage is in AppShell?
Created: 2024-04-06T14:18:21Z
Description
Is HideSoftInputOnTapped suppose to work only in AppShell?  If so it is not mentioned in the documentation.
Steps to Reproduce

Set ContentPage containing entry as MainPage.
Set HideSoftInputOnTapped to true
Clicking outside Entry in ContentPage doesn't hide the keyboard.

Link to public reproduction project repository
https://github.com/kernshen/HideSoftInputOnTappedBug
Version with bug
8.0.14 SR3.1
Is this a regression from previous behavior?
No, this is something new
Last version that worked well
Unknown/Other
Affected platforms
Android
Affected platform versions
No response
Did you find any workaround?
No
Relevant log output
No response

Duplicate issue #26792: HideSoftInputOnTapped Not Working Net9
Created: 2024-12-23T21:31:43Z
Description
In the previous version of Net MAUI (Net 8) the HideSoftInputOnTapped was working well but now with 9.0.21 version the keyboard is not hiding when the user taps outside the keyboard.

Steps to Reproduce
1 - Create a ContentPage with a Entry
2 - Set the HideSoftInputOnTapped="True"
3 - Tap in entry so that the keyboard appears
4 - Tap outside the keyboar
Error: The keyboard doesnt dissappears
Expected: The keyboard hides
Link to public reproduction project repository
https://github.com/jhovelnu/MauiApp2Net9
Version with bug
9.0.21 SR2.1
Is this a regression from previous behavior?
Yes, this used to work in .NET MAUI
Last version that worked well
8.0.100 SR10
Affected platforms
Android
Affected platform versions
No response
Did you find any workaround?
No response
Relevant log output

Closing comment (2025-04-16T20:00:36Z): Duplicate of #21681