You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maybe this is not the right repo to report it, but I'm not sure where is the right repo to report it.
Steps to reproduce
dotnet new
dotnet build
Expected behavior
TimeDateStamp(can be found at offset 0x88 in most case) should be the same as buildTime, as it used to be in netframework and other .exe files.
Actual behavior
TimeDateStamp seem to be some random number, like "0x8FF50636 (2046/7/14 16:49:58)", "0xA9161448 (2059/11/23 7:01:28)"
Environment data
dotnet --info output:
.NET Command Line Tools (2.0.0-preview2-006497)
Product Information:
Version: 2.0.0-preview2-006497
Commit SHA-1 hash: 06a2093335
Runtime Environment:
OS Name: Windows
OS Version: 10.0.16257
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\2.0.0-preview2-006497\
Microsoft .NET Core Shared Framework Host
Version : 2.0.0-preview2-25407-01
Build : 40c565230930ead58a50719c0ec799df77bddee9
And switch to 1.1.0 by global.json, and get the same result.
.NET Command Line Tools (1.1.0)
Product Information:
Version: 1.1.0
Commit SHA-1 hash: d6f4336106
Runtime Environment:
OS Name: Windows
OS Version: 10.0.16257
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\1.1.0
Microsoft .NET Core Shared Framework Host
Version : 2.0.0-preview2-25407-01
Build : 40c565230930ead58a50719c0ec799df77bddee9
Change TargetFramework to net461 didn't resolve this, but the traditional csproj with
Just mark. Add the below to your csproj if you need the timestamp, and the value of TimeDateStamp in Deterministic mode is always (value & 0x80000000) != 0
use self = Assembly.GetExecutingAssembly().Location |> File.OpenRead |> PEReader
lettimeDateStamp= self.PEHeaders.CoffHeader.TimeDateStamp |> int64 |> DateTimeOffset.FromUnixTimeSeconds
printfn "I was built at %s"(timeDateStamp.ToString("yyyy-MM-ddTHH:mm:ssZ"))
Maybe this is not the right repo to report it, but I'm not sure where is the right repo to report it.
Steps to reproduce
Expected behavior
TimeDateStamp(can be found at offset 0x88 in most case) should be the same as buildTime, as it used to be in netframework and other
.exe
files.Actual behavior
TimeDateStamp seem to be some random number, like "0x8FF50636 (2046/7/14 16:49:58)", "0xA9161448 (2059/11/23 7:01:28)"
Environment data
dotnet --info
output:And switch to 1.1.0 by
global.json
, and get the same result.Change
TargetFramework
tonet461
didn't resolve this, but the traditional csproj withworks well in the same PC(build with VS15.3.0P7.0 to use the latest rosyln as netcore be), so I'm not sure if it's an issue with rosyln.
The text was updated successfully, but these errors were encountered: