Microsoft.Extensions.Configuration.dll has wrong modified date

[sunmijiang]

Description

Runtime version .net framework 4.7.2
Create a new C# project and add reference Microsoft.Extensions.Configuration 3.1.0, build project, then you will see the following dlls have wrong modified date in the bin folder.

Reproduction Steps

Create a new C# project and add reference Microsoft.Extensions.Configuration 3.1.0, build project, then you will see the following dlls have wrong modified date in the bin folder.

Expected behavior

The modified date should be same with created date.

Actual behavior

The modified date is 1/1/1980.

Regression?

It works about one week ago.

Known Workarounds

No response

Configuration

No response

Other information

No response

Tagging subscribers to this area: @dotnet/area-extensions-configuration
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Description

Runtime version .net framework 4.7.2
Create a new C# project and add reference Microsoft.Extensions.Configuration 3.1.0, build project, then you will see the following dlls have wrong modified date in the bin folder.

Reproduction Steps

Create a new C# project and add reference Microsoft.Extensions.Configuration 3.1.0, build project, then you will see the following dlls have wrong modified date in the bin folder.

Expected behavior

The modified date should be same with created date.

Actual behavior

The modified date is 1/1/1980.

Regression?

It works about one week ago.

Known Workarounds

No response

Configuration

No response

Other information

No response

Author:	sunmijiang
Assignees:	-
Labels:	untriaged, area-Extensions-Configuration
Milestone:	-

[eerhardt]

This appear to only happen with the 3.1.0 nuget package. If I use the latest 3.1 version, 3.1.27, it doesn't occur.

Since we can't fix 3.1.0 (because nuget packages are immutable), this can't be fixed. My suggestion is to update to the latest 3.1.27 which contains the latest servicing fixes.