Zou Wei
Zou Wei
BTW, I found a possibly related post on SO: ['Could not load file or assembly 'netstandard, Version=2.0.0.0, …'. Reference assemblies should not be loaded for execution](https://stackoverflow.com/q/45021965/3427520).
After adding some more probePath to the project file, the original `Could not resolve assembly: netstandard` error is gone. ```xml W:\VS2017\MyApp\bin\Release\PublishOutput W:\VS2017\MyApp\bin\Release\PublishOutput\runtimes\win\lib\netcoreapp2.0 C:\Program Files\dotnet\sdk\2.0.0\Sdks\Microsoft.NET.Sdk\tools\net46 C:\Program Files\dotnet\sdk\2.0.0\Microsoft\Microsoft.NET.Build.Extensions\net461\lib ``` But new errors...
> @zwcloud have you eventually resolved this problem? No, I gave up. I was just trying ModPhuserEx.
@0xFireball It works for me. But unfortunately, I got the following error when trying to run my .NET core console app. > Unhandled Exception: System.TypeInitializationException: The type initializer for ''...
> > > Yes, that should work. No. That doesn't work. I have tried.
The demo project should run without problem, but they haven't been tested for a long time. Maybe I broke something when developing child window rendering. I'll look into the issue...
Seems to be a GPU-specific issue. I cannot reproduce the error on win10 and NVIDIA 1070Ti/2080Ti. Please try disable MSAA by setting `Application.EnableMSAA` to false, and run the demo again....
> when closing the window the > following exception appears: > > *System.InvalidOperationException: 'Wgl.MakeCurrent failed, error: Invalid > controller.'* This is a known issue. I will fix it later.
No. I won't use apache or bsd for Hello ImGui publicly. But I can provide a special license for single project or person if I want. BTW Hello ImGui is...
fixed missing border and clipping: 