Marek Fišera
Marek Fišera
That is a good point. Unfortunately the only idea I have is to pack Plugin Manager as a resource inside Git Extensions and extract it on the first run when...
> Can we use the "default user account"? This is interesting idea. We could allow to specify if a plugin should be installed "for everyone" or "just me" and default...
Error boundaries to the rescue.
Most of the source code is already refactored into `ExpenseCardContext` and `ExpenseCard`. I don't see much oportunity for more reuse.
I'm sorry for late reply. IIRC the issue correctly, it's about using Console.In or stdin, that is not supported on WebAssembly https://github.com/maraf/runtime/blob/main/src/libraries/System.Console/src/System/ConsolePal.WebAssembly.cs#L108 There isn't such a thing as stdin in...
@PawelStadnicki ☝️ (fixing the ping above 😉)
```csharp Console.SetIn(new StringReader("Hello from custom stdin!")); var line = Console.ReadLine(); ``` This works on wasm. So if F# kernel somewhere touches stdin reader, this seems like a workaround EDIT: It...
All the APIs are marked with `SupportedOSPlatform` https://learn.microsoft.com/en-us/dotnet/standard/analyzers/platform-compat-analyzer. So we need to analyze F# kernel for `browser-wasm` RID
> Let's say we want to load Nuget package The AssemblyLoadContext works on wasm (so you can dynamically load additional assemblies)
This one is a bit complicated. When a first feed returns enough packages, other feeds are not even searched. PM doesn't know if there are same packages with higher versions...