This is not an official bump to netstandard 2.0 right ?

Be careful with the Google.Protobuf upgrades, they made some significant changes from 3.0 -> 3.3 around code generation of enums, which made for a pretty painful upgrade. Hopefully the 3.2 -> 3.4 is less of a headache for c#.

@joshgarnett could you show an example, please? I did not see any breaking changes in Google.Protobuf/Tools

@Danthar No, it is not related with netstandard2.0. I'm just trying to update the tooling

From 3.0 -> 3.2 (?) the C# code generation changed enums from upper snake case to upper camel case. ex: FOO_BAR to FooBar. It create a big headache of a refactor for me on my project. I don't know of any similar changes for 3.2 -> 3.4. I mainly just wanted to call it out as something to watch out for.

@joshgarnett @alexvaluyskiy why include any Protobuf upgrades right now? Just drop them?

Although, I guess it should be ok since all of that stuff is internal and this doesn't affect wire compatibility, right?