Hank McCord
Hank McCord
> @avidenic Yes, the problem is that **.NET Standard 2.0** is not compatible with **.NET Core 3.x**. This library should have support for **.NET Standard 2.1** to be compatible with...
Here's the direct link to the recommended workaround: https://github.com/dotnet/wpf/issues/6792#issuecomment-1183633402 Put that in either your csproj or a `Directory.Build.targets` file.
Ditto. I've got the same issue as well as my buddies when RatScanner is open. You have to get a 2nd person to tell you whether or not the stream...
@Blightbuster I came up with a solution (I do some SetWindowLong stuff in my [ReadySetTarkov](https://github.com/InKahootz/ReadySetTarkov) program). See my PR. Tested it with my buddies who said my stream **was** working...
I think I could help as well! I'll submit some code and you can take a look at it.
I submitted a PR for the manifest: https://github.com/microsoft/winget-pkgs/pull/28191/ You should be able to find/install it once it auto-completes.
@KirillOsenkov It is now in the index. So I think this issue can be closed. I'm sure we could automate the process but I didn't see automation for chocolately yet...
Confirming as well. Only "primary" browser window shows correct badge text.
@Araxeus That wouldn't help anyhow. `sign-addon` 6.0.0 still depends on `request` 2.88.2
You can specify the authority host via an environment variable before using azuresigntool. This is how I use it in our pipelines to connect to Azure Gov. ```pwsh $env:AZURE_AUTHORITY_HOST="https://login.microsoftonline.us/" azuresigntool...