Export with Stride fails

vvvv gamma bug
1 
Cleaning build directory (C:\Users\user\Documents\vvvv\gamma-preview\Exports\src)
Generating project files (this may take up to a few minutes)
Example Poles in the Wind
Building projects
dotnet publish -c Release --self-contained false /clp:ErrorsOnly /nologo "C:\Users\user\Documents\vvvv\gamma-preview\Exports\src\Example Poles in the Wind\Example Poles in the Wind.csproj"
Unable to build C:\Users\user\Documents\vvvv\gamma-preview\Exports\src\Example Poles in the Wind\Example Poles in the Wind.csproj. Reason:
C:\Users\user\.nuget\packages\stride.core.assets.compilerapp\4.2.0.2121\buildTransitive\Stride.Core.Assets.CompilerApp.targets(153,5): error MSB3073: Der Befehl ""C:\Users\user\.nuget\packages\stride.core.assets.compilerapp\4.2.0.2121\buildTransitive\..\lib\net8.0\Stride.Core.Assets.CompilerApp.exe"  --disable-auto-compile --project-configuration "Release" --platform=Windows --project-configuration=Release --compile-property:StrideGraphicsApi=Direct3D11 --output-path="C:\Users\user\Documents\vvvv\gamma-preview\Exports\src\Example Poles in the Wind\bin\Release\data" --build-path="C:\Users\user\Documents\vvvv\gamma-preview\Exports\src\Example Poles in the Wind\obj\stride\assetbuild\data" --package-file="C:\Users\user\Documents\vvvv\gamma-preview\Exports\src\Example Poles in the Wind\Example Poles in the Wind.csproj" --msbuild-uptodatecheck-filebase="C:\Users\user\Documents\vvvv\gamma-preview\Exports\src\Example Poles in the Wind\obj\Release\stride\assetcompiler-uptodatecheck"" wurde mit dem Code 1 beendet. [C:\Users\user\Documents\vvvv\gamma-preview\Exports\src\Example Poles in the Wind\Example Poles in the Wind.csproj]

----
There was a problem exporting your Application.
Please check for solutions by clicking the "Troubleshooting" button.

I am getting this error on 2 different machines, with stable 6.6 and preview 6.7
The PC with 6.6 is also freshly set up and the gamma install is the first ever. Patches with no stride dependency seem to export just fine.

2

Does this workaround solve the issue?

3

yes, thanks. was reading the troubleshooting but missed MSB3076