Alex
Alex
Same issue here, however, the packaged was published successfully
> This is still an issue. There is a good [fork](https://github.com/alirezanet/publish-nuget) of it. Simply replace this part in your workflow with alirezanet/[email protected] and your are done
If other functions of this workflow like tagging are not needed, using `dotnet nuget push` directly is of course a viable and probably a better option :)
The important part from the Stackoverflow link above: > [..] this is normal behavior. The constructor of the XmlSerializer first tries to find an assembly named [YourAssembly].XmlSerializers.dll which should contain...
Couldn't this be solved with Triggers?
Not yet. But since support for Postgres has been added, I plan to integrate it into one of my projects soon.
 The $130 must be this community support and elevation they are talking about :D
> [..] we are a small commercial shop and there is no way I will get approval for this license. I also don't want to have to completely rewrite all...
This works so much faster, thanks a lot @soenneker