-
Notifications
You must be signed in to change notification settings - Fork 588
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
Upgrade fcs and fscore #1534
Upgrade fcs and fscore #1534
Conversation
…rkaround for fsharp/fsharp#672), filter Microsoft.FSharp.Core.netcore (workaround for fsharp/fsharp-compiler-docs#715)
… remove some old hacks and unused packages. Try to make tests run again...
…. Fix different behavior of Mono.Cecil after upgrade (AssemblyReader now need to be disposed to 'unlock' the file).
|
nice! 🎊 |
There is a mono bug related to the script caching when running on mono 5.0.0.76. I saw this yesterday. Remove the caching code and it's fine. |
? |
Whats the caching code? @nosami |
Fake.FSIHelper.handleCaching - looks like code that reuses a compiled temporary assembly if it's available and valid. |
yes we should invalidate. @matthid can we do that via release? |
This is definitely a big improvement though. I am able to build FSharp.Compiler.Service with the latest FAKE. Before this change, I was seeing
|
these circular dependencies between projects are sometimes meh ;-) |
"CACHING ERROR - please open a issue on FAKE and /cc @matthid" haha! |
@nosami Does it work if you delete the caching folder? I guess its not? |
error FS0193: Specified method is not supported. ^^ is probably the error |
@nosami can you link the mono bug as well? |
I need to come up with a smaller repro I think before I create a mono bug ticket. |
Fixed by fsharp/fsharp-compiler-docs@7a8aa63 |
so what should we do? |
I'll investigate |
Fixed by mono/mono#4769 |
... trying to cherry pick to make merging easier later (hopefully)...