-
Notifications
You must be signed in to change notification settings - Fork 113
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
CSharpRepl doesn't work on .NET 6 Preview ("Version string portion was too short or too long") #8
Comments
Interesting, thanks for reporting! I also have .NET 6 Preview 4, and csharprepl is working, but I think you're right that .NET 6 probably has something to do with it. Could you please run |
Ah, I managed to recreate this by setting the |
Thanks a lot for looking into it! Here's my Click to expand
|
When we're determining the shared framework implementation paths, we parse the version number to a `System.Diagnostics.CodeAnalysis.Version` so we can choose the latest point release (so e.g. 5.0.10 comes after 5.0.9, which wouldn't be the case for normal string sorting). However, for preview versions of .NET, the version string has a trailing identifier, e.g. `6.0.0-preview.4.21253.7`, which causes `System.Diagnostics.CodeAnalysis.Version` to throw. Note, unit tests were failing when targeting `net6.0`; this fixes them all. fixes #8
This fix shipped in version 0.2.2, thanks! You can update via: dotnet tool update -g csharprepl It may take a bit of time before the package is available globally via NuGet.org. |
Thanks for the quick fix, works great! Looking forward to trying this out, I've been wishing for a good C# repl experience outside of Visual Studio for quite some time. |
Hello!
When I start CSharpRepl I'm presented with this error:
Attempting to type any character results in this exception:
However, it works fine on my laptop. A noteworthy difference between the two machines is that my desktop has .NET 6 Preview 4 installed while my laptop does not. Based on the error I'm assuming that's the culprit (something choking on the pre-release suffix?), but I did not have a chance to dig very far so that might be a red herring.
The text was updated successfully, but these errors were encountered: