toniarnold / aspnettest Goto Github PK

In theory, SHDocVw.InternetExplorer once required the Single-Threaded Aparment (STA), but this was no longer the case in the given context on Win10. Probably since Win10 update 1809 (retarded April 2019 version), even enforcing Apartment(ApartmentState.STA) (missing in .NET core) on the TestFixture causes the DocumentComplete event to time out after the second request – surprisingly, there is no difference whether the TestFixture nominally runs in the STA or the MTA.

Only workaround known today (tedious): A Visual Studio breakpoint at the end of IEExtensionBase.SetUpIE(), thus after each IE startup, precariously restores the old behavior and usually causes the tests to pass.

Steps to reproduce:

1. Create a new clone for a NuGet-only binary build according to the NuGet-only guide.

2. Open minimal.nuget.core.sln, restore NuGet packages and build the solution. This error message is only generated on the first build or when rebuilding (which takes some time due to the COM reference):

The assembly path obj\Debug\netcoreapp2.1\Interop.SHDocVw.dll is invalid. Assembly paths must be rooted.
minimal.nuget.core
C:\Program Files\dotnet\sdk\NuGetFallbackFolder\microsoft.aspnetcore.razor.design\2.1.2\build\netstandard2.0\Microsoft.AspNetCore.Razor.Design.CodeGeneration.targets
69

3. Build once again. The error message disappears and the solution compiles. Unlike in minimal.nuget.webforms.sln, the Interop.MSHTML.dll and Interop.SHDocVw.dll are copied automatically to the ./bin directory.

4. Run the web application with .\minimal.core\run.bat. It only seems to be working, as .cshtml Razor pages are not interpreted, only served literally, like static pages.

There is no problem when referencing the COM DLL indirectly as in the minimal.core.sln source solution.

Since a forced upgrade to .NET 5 (for Blazor .NET 6), DbContext Core requires DI Logging, thus unit tests requiring DbContext fail in the VS Test Explorer.

As soon as asplib.blazor gets referenced in test.core, we get a MissingMethodException at LoggerFactory.Create(). If the reference is only removed, the DbTest tests using DBContext pass. Problem is the reference to Microsoft.AspNetCore.Components.Web.

Steps to reproduce:

• Open asp.websharper.sln
• Rebuild the asp.websharper.spa.fs
• wsfsc.exe (the F# compiler) crashes with:

Schweregrad Code Beschreibung Projekt Datei Zeile Unterdrückungszustand
Fehler MSB6006 "wsfsc.exe" wurde mit dem Code 1 beendet. asp.websharper.spa.fs c:\program files (x86)\microsoft visual studio\2019\community\common7\ide\commonextensions\microsoft\fsharp\Tools\Microsoft.FSharp.Targets 281

This happens both on VS2019 and VS2022. FSHarp.Core is the current 5.0.2, WebSarper the current 5.0.0.120

In resease v0.2.0, when two concurrent page requests have an overlapping time span from the initial HTTP request to the following SignalR request, one can accidentally get the other's database-persisted object instance.

Fixed in the b0.2.1 branch with the ScopeCorrelation service.