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

#r "nuget:..." fails to load net8-windows only nuget #17987

Open
goswinr opened this issue Nov 10, 2024 · 1 comment
Open

#r "nuget:..." fails to load net8-windows only nuget #17987

goswinr opened this issue Nov 10, 2024 · 1 comment
Assignees
Labels
Milestone

Comments

@goswinr
Copy link
Contributor

goswinr commented Nov 10, 2024

in FSI:
I believe the temporary *.fsproj created by #r "nuget:..." should be targeting the current OS.
so net8.0-windows instead of just net8.0.

Currently, my scripts in Fesh fall back to the net472 target and report a warning because they can't resolve the net7.0-windows7.0 target .

C:\Users\gwins\.packagemanagement\nuget\Projects\1712--947df84f-bc09-48fd-bfc6-6085e18da546\Project.fsproj : warning NU1701: Package 'Fesher 0.3.0' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8, .NETFramework,Version=v4.8.1' instead of the project target framework 'net8.0'. This package may not be fully compatible with your project.

to test just put this in FSI:

#r "nuget: Fesher, 0.3.0"
open Fesher
Printfn.red "red"
@baronfel
Copy link
Member

Agree with this broadly - the scripting environment should be able to be as native as possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: New
Development

No branches or pull requests

4 participants