Skip to content
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

Closed
jogibear9988 opened this issue Jun 19, 2024 · 5 comments
Closed

Problem with Program build in Visual Studio for ARM #103685

jogibear9988 opened this issue Jun 19, 2024 · 5 comments

Comments

@jogibear9988
Copy link

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:
image

The Visual Studio for ARM Build:
image

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

@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Jun 19, 2024
Copy link
Contributor

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

@ViktorHofer ViktorHofer added needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners and removed area-Infrastructure-libraries labels Jun 19, 2024
@huoyaoyuan
Copy link
Member

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.

@jogibear9988
Copy link
Author

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...

Copy link
Contributor

Tagging subscribers to this area: @vitek-karas, @agocke, @VSadov
See info in area-owners.md if you want to be subscribed.

@vitek-karas
Copy link
Member

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.

@dotnet-policy-service dotnet-policy-service bot removed the untriaged New issue has not been triaged by the area owner label Jun 19, 2024
@am11 am11 removed the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Jul 19, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Aug 19, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Archived in project
Development

No branches or pull requests

6 participants