-
Notifications
You must be signed in to change notification settings - Fork 795
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
Coreclr compiler does not embed native resources, E.g icons for vs #1172
Labels
Bug
Impact-Medium
(Internal MS Team use only) Describes an issue with moderate impact on existing code.
Milestone
Comments
KevinRansom
added
Impact-High
(Internal MS Team use only) Describes an issue with extreme impact on existing code.
Impact-Medium
(Internal MS Team use only) Describes an issue with moderate impact on existing code.
Area-Compiler
and removed
Impact-High
(Internal MS Team use only) Describes an issue with extreme impact on existing code.
FSI
labels
May 10, 2016
@KevinRansom Has this been fixed? |
@KevinRansom Just to check - is this required in order to complete FSC on .NET Core? Just trying to work out the priority of this |
enricosada
added a commit
to enricosada/Paket
that referenced
this issue
Nov 28, 2019
to add icons with `fsc` it's possible to use native resources (like `<Win32Resource>paket.res</Win32Resource>`). the `ApplicationIcon` property is not supported either ( ref dotnet/sdk#2818 ). The `fsc` running on coreclr doesnt support yet native resources (ref dotnet/fsharp#1172 ) As workaround, a free tool (http://angusj.com/resourcehacker/) is used to add the icon after the exe is generated
This is fixed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Bug
Impact-Medium
(Internal MS Team use only) Describes an issue with moderate impact on existing code.
in fsi on a windows PC run the following script on a build made with the coreclr compiler.
outputs:
Expected output:
The text was updated successfully, but these errors were encountered: