-
Notifications
You must be signed in to change notification settings - Fork 52
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
Error when compiling Could not load file or assembly System.Runtime #1055
Comments
What .NET Core do you have installed? Can you post your output for |
Project is netcoreapp2.2 |
Just out of curiousity, what's the version on your |
Where can I view it? |
Hi, @CtrlShiftEscape, I have been testing latest templates on |
Adam and Jand42, if you are asking for peeps here to do something else to determine a version or setting value of extracting output from .netcore, please provide a link or the instructions of how to get this info, just as in code when you f12 to another function, then f12 again to the next function, ANY additional steps reduces the chances of user following your advice and thus increases the chance users will seek alternate solutions. I too failed to get this git solution to compile, my solution -> look at Giraffe it seems to work. Especially when looking at leading edge stuff like this it is silly for it not to compile. MOST people are going to be put off by it not working out of the box. |
@yetanotherlogonfail Hi, here are the .NET Core 3.0 preview releases, they are not auto-updated by the VS2019 installer https://dotnet.microsoft.com/download/dotnet-core/3.0 Having a
|
I'm running into the same issue. Steps to reproduce:
Then after modifying the
Full error that I'm getting:
Output of Output of
I don't know how to check what's the version of |
Forgot I posted this, im afraid to say that, I should read the book my son bought me more often and take its advice. "Move fast and break things". I didnt move fast enough with F#, and as a result spent way too long getting data with nulls to work and then dealing with the the fact that a language that does not automatically import namespaces, references etc for you is doomed. Giraffe was fab and worked but alas the MS bolier plate of even that was too much for me in the end. I now produce my endpoints in Go/Golang, if fast simple and just works out of the box. My original point I made here STILL applies if anyone posts an example and I mean ANYONE. it must work, out of the box nothing to be added, or else you will find folks giving up- on what maybe a fantastic solution but if you cant step through the example and see it working, it will go the way of F#. condemed in history as another failed startup. |
@yetanotherlogonfail I would love to take the "move things fast and break things" advice, and keep WebSharper and its libs on the latest netstandard/netcore and SDKs - and just switch the maintenance burden to end users then having to update their own stack constantly. But I doubt anyone would like that. We are juggling a ~100 lib ecosystem, all on a constantly moving netcore, on several OSs. Somewhere in that hierarchy, there is a mismatch with a reference. Let's find it. If anyone has info that can help, it will be quicker. This came up on the WebSharper gitter too, so I think we will have a good grip on it soon. That said, this issue got way less attention it should have, because other priorities got in the way. But rest assured, your voice is heard loud and clear. |
@CtrlShiftEscape @mjarosie @yetanotherlogonfail Sorry for the very long turnaround, I am now taking a hard look at the netcoreapp3.1 assembly redirection issues. Some WebSharper functionality such as outputting offline sitelets and locally defined macros make the compiler load the freshly compiled assembly dynamically, and the compiler for netcore is still running on netcoreapp2.0. I have tried playing around with assembly redirection in config (having no upper bounds) with no success, currently testing to multi-target the netcore wsfsc between netcoreapp2.0 (used for netstandard2.0 and netcoreapp2.x) and netcoreapp3.1 (used for netstandard2.1 and netcoreapp3.x) I think that would solve it while breaking no existing build scenarios. |
Switched to using netcoreapp3.1 for compilation with https://github.com/dotnet-websharper/core/releases/tag/4.6.4.404 |
Hi @CtrlShiftEscape @mjarosie, can you retry and let me know if you are still running into this issue? |
@granicz I just checked, it works! : ) |
All test.playlist unit tests and WebForms/MVC Core/WebSharper SPA tests are now green. When run at once, they rarely pass as a whole due to stalled web servers. A test run takes way over half an hour, primarily because Selenium.Firefox.WebDriver with Firefox is extremely slow compared with Chrome (fast) and Selenium InternetExplorer (significantly slower than IIE COM InternetExplorer). Consolidated Click() test methods across project types and added an optional awaitRemoved parameter that polls the DOM element for being removed from the DOM and an optional (higher) timeout to AssertPoll. Only this makes WebSharper SPA GUI tests reliable. Updated dependencies except WebSharper, as with 4.6.4, asplib.websharper can't even indirectly depend on the shared netstandard2.0 asplib project no more. Related: dotnet-websharper/core#1055 - the whole .\tools\netstandard2.0 directory is missing in the NuGet package, and the build fails due to the missing WebSharper.MSBuild.CSharp.
Project is created using
dotnet new websharper-html
The text was updated successfully, but these errors were encountered: