Jooseppi12
Jooseppi12
@Gastove I'll go ahead and investigate the build issue with dotnet 3.0 and get back to you with my findings. Thank you for looking into the logs of the Docker...
Created this repo with the project and the two used nuget packages: https://github.com/Jooseppi12/core-1349 The above does not build without dotnet 7.0 present on the machine, but when it is there...
6.1.7.441-net8 is out on nuget
@benedictleejh The problem is caused by the metro.js resource, as it is adding methods to the prototype, but not without specifying that they are not enumerable. This issue has come...
This is released for the WebSharper 8 packages on our GitHub feed, but was not backported to the websharper6 branch
@ingted There should be a new version on nuget (6.1.7.476) out there to remove the usage of BinaryFormatter for WebSharper 6
@rbauduin Yeah, as @granicz said above, can you try turning off the Booster process, by adding this in your project file in the PropertyGroup: `True` Also upon further investigation, the...
Hey, so after some testing there is an issue on non-windows environments with the Booster process used by the build. To work around this, you can try using `True`, which...
@mawifr Can you give some details of these projects? What WebSharper project type they are using and what dependencies are we working with?
That's quite interesting! I feel like it won't be actually a problem with the javascript transpilation, otherwise you should see that in the dotnet build as well. It would be...