Open aboudoux opened 3 years ago
Hello @aboudoux
You are the first who requested it, that's why it's not there yet.
Anyway, please try the attached NuGet package. Unsafe code is allowed by default now.
unfortunately the update does not seem to fix the problem. Do I also need to update Livesharp Server?
This is a little more complicated than I initially thought. Can you come to https://gitter.im/LiveSharp/Lobby and PM me (@ionoy)? I need to know what stuff do you expect to work in the unsafe region. Taking a pointer from a string is easy enough, but I suspect you have something more complicated there.
Hey @aboudoux
Are you using server-side Blazor? Because the most recent LiveSharp build should fix the unsafe
and other IL issues for .NET Core projects.
Hi,
We are testing livesharp for our Blazor product, and this one use some low level libraries which contains unsafe code.
So, blazor can connect to LiveSharpServer, but the log display an error due to the /unsafe switch that is not set for compilation.
To reproduce the problem, just create a new blazor server project, and replace the Counter.razor by the following code :
Check "Allow unsafe code" in the Build properties of the project, and run with LiveSharp.
Thanks for your help !