.NET SDK integration post, NuGet v1.17

[kkm000]

This is a post announcing integrated build of proto files in a C# .NET projects, upcoming in v1.17.

I hope I matched both the general philosophy and tone of the blog, but I'd be happy to make any corrections.

/cc @jtattermusch

[carl-mastrangelo]

@kkm000 Looks cool, I did a brief pass over it. Please ping this if it isn't getting attention.

[carl-mastrangelo]

Nit: it's easier to read if the verb tenses align throughout. Consider rewording this "The dotnew new command creates the file ...".

[kkm000]

I rephrased that sentence a bit, but I am not sure I grok your concern. This is as present a tense as it only could be.

[hsaliak]

This looks great, thanks for writing it up! left a few minor comments

[jtattermusch]

nit: put the tag under a separate ? That would make it more visible and it's also the style that Visual Studio would use if you added a file through the IDE.

[kkm000]

Come think of it, I'm rather inclined against this.

My thinking goes, I do not know if user's editor supports XML, and XML is nasty to type without syntax highlighting and checking from the editor. So I think for the purposes of the throwaway walkthrough this is good enough. The goal as I understand it is to make the walkthrough as smooth as possible, and XML brockets are braindead. By me, the fewer, the better.

Some people prefer to keep it neat, others just lump it all together. And MSBuild does not care.

[kkm000]

In summary, I added a 2nd paragraph from the top, above the more marker, to explain the intent better, another paragraph on dependency checking, and one sentence st the very end--it sounded to me as if it was lacking a nice closing.

Thanks for the comments everyone! Ready for the round 2!

@jtattermusch, this should not be published before the example branch is merged, I guess?

[jtattermusch]

@kkm000 yes this will only be published once 1.17.0 packages are out, so that the feature can be easily tried by everyone.

[jtattermusch]

nit: at the first sight the indent looks like it's done by mistake. Also let's make the comment more informative.

<!-- mark Grpc.Tools as build-only dependency by adding PrivateAssets="All" attribute -->

[kkm000]

Done, does this read better? Not really sure if the shouty-cased "IMPORTANT" is appropriate.

[jtattermusch]

I think the blogpost is looking good, thanks for writing it!

I'll merge (and publish the blogpost) once the v1.17.0 release is out, nugets are pushed and the examples PR is merged.

[kkm000]

Super, thank you!

[carl-mastrangelo]

This post will tentatively go out tomorrow. @kkm000, would you be able to rename the post to 12-18-18 so that it appears as the newest post on the https://grpc.io/blog/ list?

[kkm000]

@carl-mastrangelo Done.

[jtattermusch]

Let's merge?

[jtattermusch]

Things are looking good, so I'll go ahead and merge.

[kkm000]

Looks weird, no heading or the pre-cut paragraphs. Is there some indexing that has to happen, or is something wrong with formatting?

[kkm000]

Just realized, this: https://github.com/grpc/grpc.github.io/blob/master/_posts/2018-18-18-grpc-dotnet-build.md shows the keywords as a block, but this https://github.com/grpc/grpc.github.io/blob/master/_posts/2018-12-11-grpc-stacks.md as table. The parser does not like something. Quotes around 'kkm'? No other ideas, really!

[kkm000]

It's the : in title, see https://github.com/kkm000/grpc.github.io/blob/c683dacb6f22518fe5ae1d33da83e71a37fca8e7/_posts/2018-18-18-grpc-dotnet-build.md

[jtattermusch]

Good catch, do you wanna create a PR to replace : with -?

[kkm000]

Here is a couple of solutions, trying both. Quotes seem less ugly that the hex code. Just a sec.

[kkm000]

jekyll/jekyll#549

[kkm000]

@jtattermusch, #798. Looks like a table, similar to other .ms files.