András Jankó

@fischgeek @granicz Some testing bring us closer: 1. the F# code being executed seems to be the correct, current one. Only WebSharper.UI.Templating type provider is caching incorrectly 2. If you...

@fischgeek Hello, this is now fixed in WebSharper.UI hotfix release https://github.com/dotnet-websharper/ui/releases/tag/6.0.0.230

@cgravill @granicz Hello, targeting netstandard2.0 and netstandard2.1 are still fully supported, WebSharper's own core libraries are using it too https://github.com/dotnet-websharper/core/blob/master/src/stdlib/WebSharper.Main/WebSharper.Main.fsproj#L3 As for the original metadata format issue, indeed it is...

@Jooseppi12 See #1161. Squiggles _do_ show up for a moment, but VS overrides errors from build quickly from those coming from normal F# code service. Maybe error subcategory can help,...

After more investigation and experimenting, I don't think we can do this is current Visual Studio. IntelliSense errors always seem to hide build errors. This needs standardized F# analyzers to...

This analyzer could also treat `IsClient` specially as in #730. Client-only calls in a false path would give a compile-time error.

@granicz @Jooseppi12 Additional ideas: * The JavaScript attribute now has a constructor overload that takes a JavaScriptOptions enum for some rare use cases (optimized interface proxying in WS.Main, ignoring type...

Example error: ``` The type initializer for 'WebSharper.Moment.Tests.Site' threw an exception. ---> System.TypeInitializationException: The type initializer for '.$Samples' threw an exception. ---> System.BadImageFormatException: Could not load file or assembly 'Microsoft.AspNetCore.Mvc.Abstractions,...

TP is called twice per WS compilation, F# compilation and then for inspecting type checking results. The latter is never disposed and the assembly resolver event handler added in ProvidedTypes.fs...

@granicz Yes, sadly F# compiler locks in TP assemblies, this is an annoyance when developing TPs in Visual Studio too... I see no other workaround for now than wsfscservice somehow...