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

Use SDK version 6.0.101 #216

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from
Draft

Conversation

charlieturndorf
Copy link

@charlieturndorf charlieturndorf commented Jan 23, 2022

Updated the .NET SDK version in global.json to 6.0.101. This just allows the latest SDK to be used during builds (which was the simplest way to build FsiRefGen submodule on .NET 6).

Actual target framework is still netstandard2.0 in case anyone is using Hopac on .NET Framework or other older platforms.

Edit: I needed to change the AppVeyor image to Visual Studio 2022 for SDK 6.0.101 support.

Updated the SDK version in global.json to 6.0.101
@charlieturndorf charlieturndorf marked this pull request as draft January 23, 2022 04:10
Using AppVeyor's Visual Studio 2022 image should allow us to build with .NET SDK 6.0.101
@charlieturndorf charlieturndorf marked this pull request as ready for review January 23, 2022 04:21
@charlieturndorf charlieturndorf marked this pull request as draft January 25, 2022 07:00
@charlieturndorf
Copy link
Author

After building my main codebase with .NET SDK 6, I'm getting TypeLoadExceptions when the runtime goes to load certain F# generic types. Everything works fine if I build with .NET SDK 5.

Possibly related to dotnet/sdk#22258

I want to isolate this issue and make sure it's not going to affect Hopac. (Just to be clear, I don't have any direct evidence that it does actually affect Hopac.)

@charlieturndorf
Copy link
Author

I've isolated the issue I was having with .NET SDK 6, and reported dotnet/fsharp#12645. (I believe the TypeLoadExceptions I was seeing earlier were caused by crashes due to stack overflow.)

So building Hopac releases with .NET SDK 6 should be ok, but I'll leave this PR as draft until I hear more.

@charlieturndorf
Copy link
Author

I also realized we would need to look more into the cause of #212 before this could be merged. The BadImageFormatException was alleviated by rolling back to dotnet 3 in #213 but I don't think the cause was fixed.

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

Successfully merging this pull request may close these issues.

None yet

1 participant