@adamcai contributions are welcome, at least I plan to release this next version of pythonnet:

#165

Let me know if you would like to add Python 3.6 support, then I can add you on nuget.

I'm happy to take a look at this, let me know what needs to be done. I've created nugget packages directly, and via Appveyor on another project.

i like nugget :) i added you @Cronan to package owners. feel free to add Python 3.6 version. We should probably start adding pythonnet 2.4.0.dev versions in all distributions channels (nuget, pypi. conda, docker).

for remaining issues with nuget please review the linked issue #165.

Have all the current packages been built "by hand", or do you have some appveyor integration?

I'll investigate doing it from Appveyor

@Cronan any update on this? I only see 2.7 and 3.5 on Nuget at the moment.

@chrisjbremner would you like to make these nuget builds?

I was able to build the DLL from the solution file provided in the repo (didn't realize it was there when I made the comment), which worked for my purposes

Same here, a 3.6 nuget package would be nice. Willing to do it myself, it's been a year =(

@Gaspa79 would you like to make this contribution?

I am willing to make this contribution. :)
You are welcome to examine the build artifacts of my fork in Appveyor: https://ci.appveyor.com/project/inna-w/pythonnet/builds/24890622.
Only --xplat builds produce the nuget package, since I am utilizing MSBuild 15 capability to generate package as part of the solution build process.
If we are happy, I will submit a pull request.