-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[5.0.100-preview.6.20308.7] OpenMu button disabled #37640
Comments
I couldn't figure out the best area label to add to this issue. Please help me learn by adding exactly one area label. |
@DotNetAppCompatFeiWang thanks, note you can add triple back ticks (`) on their own line to get pretty formatting, I did that above. https://github.github.com/gfm/#fenced-code-blocks |
I don't have context here but the diff between the two blocks above is the addition of this
|
@steveharter the suggestion here is that the JsonSerializer is emitting more JSON in Preview 6 than in Preview 5 and that it's causing a problem. Any thoughts about why that might be, since the app did not change? 1). Windows 10 RS5 X64 + .NET Core SDK build 5.0.100-preview.6.20308.7: Fail |
BTW ther'es a bit more info in the internal link above. |
This is related to #36936.
The change at the heart of this issue is #32107 which added code to enable edge-case scenarios like the following (i.e to serialize a public property that was hidden by a non-public property): var obj = new ClassWithNewSlotPrivateProperty();
string json = JsonSerializer.Serialize(obj); public class ClassWithPublicProperty
{
public string MyString { get; set; } = "DefaultValue";
}
public class ClassWithNewSlotPrivateProperty : ClassWithPublicProperty
{
private new string MyString { get; set; } = "NewDefaultValue";
} Expected: Following the fix in #37720, it is only in the above edge-case scenario that the serializer will emit more output. |
@DotNetAppCompatFeiWang looks like your diagnosis was correct, thanks for helping narrow this down to the correct component, that saves a huge amount of time. |
@layomia can you please help to confirm the fix is merged to Preview7 branch? This issue still repro with the latest Preview7 build dotnet-sdk-5.0.100-preview.7.20351.2. |
@layomia Just want to check again with you, can you please help to confirm the fix is merged to Preview7 branch? This issue still repro with the latest Preview7 build dotnet-sdk-5.0.100-preview.7.20351.2. |
The PR that was linked appears to be:
|
@layomia can you help with the question about the fix not working. |
@DotNetAppCompatFeiWang @danmosemsft - sorry for the delay. I'm investigating why the issue is not fixed with this change #37720. I have the repro machine set up and will be in touch offline about getting the full suite of app compat tests that run the serializer. My target for a fix, if any, would be the preview 8 snap on Jul 15. Depending on my investigation, we may have to document a breaking change for this and related edge case scenarios, and modify the tests accordingly. |
Verify this issue fixed in build dotnet-sdk-5.0.100-preview.8.20373.19-win-x64 |
Application Name: Open Mu
OS: Windows 10 RS5
CPU: X64
.NET Build Number: 5.0.100-preview.6.20308.7
App Location: On repro machine, at C:\Users\appcompat\Documents\OpenMU
App Source : On repro machine, at C:\Users\appcompat\Documents\OpenMUSource
App Source on GitHub link: https://github.com/MUnique/OpenMU
Verify Scenarios:
1). Windows 10 RS5 X64 + .NET Core SDK build 5.0.100-preview.6.20308.7: Fail
2). Windows 10 RS5 X64 + .NET Core SDK build 5.0.100-preview.5.20279.10: Pass
3). Windows 10 RS5 X64 + .NET Core SDK build 3.1.300 Pass
Repo Machine Environment Info :
.NET SDK (reflecting any global.json):
Version: 5.0.100-preview.6.20306.2
Commit: ca518bb33e
Runtime Environment:
OS Name: Windows
OS Version: 10.0.18363
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\5.0.100-preview.6.20306.2\
Host (useful for support):
Version: 5.0.0-preview.6.20305.6
Commit: 4ba9eca
.NET SDKs installed:
3.1.300 [C:\Program Files\dotnet\sdk]
5.0.100-preview.6.20306.2 [C:\Program Files\dotnet\sdk]
.NET runtimes installed:
Microsoft.AspNetCore.All 2.1.18 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.18 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.4 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.0-preview.6.20305.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.18 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.0-preview.6.20305.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.4 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 5.0.0-preview.6.20305.4 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Repro steps:
On the repo machine (10.159.67.185)
4)In Browser, Open http://localhost:1234/admin
Since "C:\Users\appcompat\Documents\OpenMU\MUnique.OpenMU.Startup.runtimeconfig.json" set to .net5 , app will use .NET5 runtime. This is issue is not repro on .NET Core 3
Expected Result:
Should be able to click StartButton, when we move cursor on top of button, click is disabled
Players should have number ex: 1/1000 instead of /1000
Total Players should be 0 instead of NaN
See Attachment : ExpectedOpenMu.png
Actual Result:
See Attachment : ActualOpenMu.png
Findings :
We think this is related to serialization, we serialize same object with .net core 3 and 5 with, it gets different results, see attachment for full json.
string jsonString = JsonSerializer.Serialize(currentConnectServerInfos);
.net core 3 :
.NET 5 Prev 6 :
Repro machine could be found at: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1138494
cc @dotnet-actwx-bot
The text was updated successfully, but these errors were encountered: