-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Problem with Program build in Visual Studio for ARM #103685
Comments
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries |
Looks similar to #63144 The screen shot you are showing are about executable files, not the managed assembly. In .NET Core there's no longer AnyCPU exe. |
I know that they are of exe files: "The DLLs seem to be the same, but the exe's are different". yes seams to be the same issue... |
Tagging subscribers to this area: @vitek-karas, @agocke, @VSadov |
This is a duplicate of #63144. .NET 6+ doesn't have the ability to produce an executable which works on multiple architectures, unlike .NET Framework. |
Description
We have a Program wich runs TT templates wich is forked from Mono (Cause the one delivered with Visual Studio still does not use NetCore) (https://github.com/dotnetprojects/SubSonic.Core.TextTemplating).
The Problem now is, if we build it on Windows X64, we can use it to Parse the Templates on Windows, but not on Windows fro ARM. Same is true for Windows for ARM, If we build it there, it is not usable on WIndows.
As we build for "Any CPU" the Files should work on both (I think), but they do not.
I've compared the exe files via: Info
I've created a small Tool to compare the DLL headers: https://github.com/dotnetprojects/DotNetFileInfo
The DLLs seem to be the same, but the exe's are different:
See the Screenshots with the differences:
The Visual Studio X64 Build:
The Visual Studio for ARM Build:
Reproduction Steps
Compile the Project in Visual Studio X64 and compile another one in Visual Studio ARM.
Expected behavior
The Projects should be the same
Actual behavior
The Projects are different
Regression?
No response
Known Workarounds
No response
Configuration
No response
Other information
No response
The text was updated successfully, but these errors were encountered: