-
Notifications
You must be signed in to change notification settings - Fork 301
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
Updated FCS to latest #3564
Updated FCS to latest #3564
Conversation
ncave
commented
Oct 23, 2023
•
edited
Loading
edited
- Updated FCS to latest (bd66d54).
Thanks for this @ncave! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As the tests are green, it looks good to me.
Should we keep the PR open and wait for the official .NET 8 release?
Or because everything seems good, should it be included in the next Fable release?
It might be interesting to have an alpha of this if that is possible. People could play around with this ahead of the official release. |
@MangelMaxime Feel free to merge before next release, if you're ok with it. |
Hi @ncave
Would it be possible to do this as well for the other projects in
I'm still able to build the compiler project. |
Are you trying to build it with .NET 6.0? I haven't tried building those other projects in the solution. I don't think you can build FCS with .NET 6.0, or at least not anymore, without making some changes. What I meant above was that dependency package downgrade makes those errors disappear when the package is consumed on .NET 6.0, i.e. makes it possible to consume the Technically you don't need to build anything else besides I hope that clarifies it a bit, let me know if it doesn't. |
Thanks, I'm building using SDK dotnet 8 RC 2. Building that test project didn't work for me, but I don't think that is related to the downgrade:
|
@nojaf Strange, could be some nuget cache thing. It restores and builds fine for me on WSL2 with .NET 8.0 RC2. Anyway, if you have to, you can reference a newer <PackageReference Include="Fable.Core" Version="4.1.1" /> Actually, looks like the latest version is |
I am still confused with the issue, FCS is ns2.0/ns2.1, all the dependencies should as well be ns2.0/ns2.1, I don't see why do those errors appear. |
@vzarytovskii Some sort of packaging issue? I'm not really sure, but it should be easy to reproduce, even with a C# project. |