5 ms·

Point taken. We have some improvements to make on this front.

by runfaster2000 9y ago

old-gregg 9y ago
Rooting for you guys. Lots of bad-ass tech has been locked up on Windows for years, can't wait to see it everywhere.
wslh 9y ago
I know you are in the .NET team but we have critical issues with Microsoft (we are MSDN subscribers) that are not addressed. The most critical issue is the impossibility to pass automated tests and sign a network device driver because of a Windows 10 bug! If you can help routing this inside the organization would be great. More info about the issue here: https://social.msdn.microsoft.com/Forums/SharePoint/en-US/b1fd3d1a-44a2-4138-9370-cd1409293697/sparta-miniport-interfaces-failed-to-start-in-windows-10?forum=whck&forum=whck https://social.msdn.microsoft.com/Forums/SharePoint/en-US/b1...
- runfaster2000 9y ago
  Sorry to hear that. I suggest calling support. Cross-org bug routing isn't super easy.
dafrankenstein2 9y ago
but i have found driver development docs appealing. also its good if u allow to download offline version of the docs.
avtar 9y ago
The Python and Django docs are great examples of how stellar reference material can be maintained for every release. https://docs.djangoproject.com/en/1.11/intro/ https://docs.djangoproject.com/en/1.11/intro/ https://docs.djangoproject.com/ https://docs.djangoproject.com/
jacques_chester 9y ago
Speaking of names and versions -- while working on Cloud Foundry Buildpacks we frequently turned our brains into pretzels trying to manage what components were versioned how. We even had custom logic to parse a YAML file where we maintained a mapping to keep things straight. Especially since some components embedded different versions of other components. I don't know if the situation has improved since I rotated off, but a bog-ordinary semver scheme would've saved a world of pain. Failing that, a single page with components (SDK? Runtime?) and available version numbers that gets updated. Because we mostly wound up working what was what from forensic readings of scattered blog posts, Github release and I think comments on Github issues. In any case, I am sure the team would be glad to give you feedback on their experiences since then -- my email is in my profile if want me to pass anything along.
- runfaster2000 9y ago
  See: https://github.com/dotnet/designs/issues/2 https://github.com/dotnet/designs/issues/2
  - jacques_chester 9y ago
    Thankyou! I will ping my colleagues tomorrow.
    - runfaster2000 9y ago
      BTW: Your friends can also contact me -> rlander@ms
      - jacques_chester 9y ago
        The thankyous keep rolling. I also remembered I can point you at the Slack instance where they live -- https://slack.cloudfoundry.org/ https://slack.cloudfoundry.org/, in the #buildpacks channel.
tzs 9y ago
One then that would have seriously helped me a few months ago, when I did a little project to learn some C# and write a command line tool using .NET Core would be a simple list of "using" statements that I'm likely to see in C# books and other documentation that are not available in Core (or that need configuration or settings changes to make work). (Or maybe the other way...a list of all "using" statements that work out of the box). The command line tool I was trying to write was to read my Safari reading list on my Mac, and construct an HTML page that contains the same information that I could put on my website, where I could then access it from my Surface Pro. Apple provides a way to export the reading list in XML, so that was my input. I don't remember what it was now, but my first approach used some XML stuff that I got out of examples from some recent C# book, and it worked fine in Visual Studio Community Edition on my Windows gaming machine. In Core, though, on my Mac (and on my Surface Pro and Windows gaming machine) it failed to build. It was not finding something I was trying to include via "using". I was not able to figure out if that thing is simply not part of Core, or if some build setting somewhere has to be changed to make it available. (I eventually changed my approach and dealt with the XML through LINQ instead of at a lower level, so that I no longer needed whatever it was whose "using" was giving me trouble, and successfully got access to my Reading List from my Surface Pro).

Point taken. We have some improvements to make on this front.

Rooting for you guys. Lots of bad-ass tech has been locked up on Windows for years, can't wait to see it everywhere.

wslh 9y ago

I know you are in the .NET team but we have critical issues with Microsoft (we are MSDN subscribers) that are not addressed. The most critical issue is the impossibility to pass automated tests and sign a network device driver because of a Windows 10 bug! If you can help routing this inside the organization would be great. More info about the issue here: https://social.msdn.microsoft.com/Forums/SharePoint/en-US/b1fd3d1a-44a2-4138-9370-cd1409293697/sparta-miniport-interfaces-failed-to-start-in-windows-10?forum=whck&forum=whck https://social.msdn.microsoft.com/Forums/SharePoint/en-US/b1...

runfaster2000 9y ago
Sorry to hear that. I suggest calling support. Cross-org bug routing isn't super easy.

dafrankenstein2 9y ago

but i have found driver development docs appealing. also its good if u allow to download offline version of the docs.

avtar 9y ago

The Python and Django docs are great examples of how stellar reference material can be maintained for every release. https://docs.djangoproject.com/en/1.11/intro/ https://docs.djangoproject.com/en/1.11/intro/ https://docs.djangoproject.com/ https://docs.djangoproject.com/

jacques_chester 9y ago

Speaking of names and versions -- while working on Cloud Foundry Buildpacks we frequently turned our brains into pretzels trying to manage what components were versioned how. We even had custom logic to parse a YAML file where we maintained a mapping to keep things straight. Especially since some components embedded different versions of other components. I don't know if the situation has improved since I rotated off, but a bog-ordinary semver scheme would've saved a world of pain. Failing that, a single page with components (SDK? Runtime?) and available version numbers that gets updated. Because we mostly wound up working what was what from forensic readings of scattered blog posts, Github release and I think comments on Github issues. In any case, I am sure the team would be glad to give you feedback on their experiences since then -- my email is in my profile if want me to pass anything along.

runfaster2000 9y ago
See: https://github.com/dotnet/designs/issues/2 https://github.com/dotnet/designs/issues/2
- jacques_chester 9y ago
  Thankyou! I will ping my colleagues tomorrow.
  - runfaster2000 9y ago
    BTW: Your friends can also contact me -> rlander@ms
    - jacques_chester 9y ago
      The thankyous keep rolling. I also remembered I can point you at the Slack instance where they live -- https://slack.cloudfoundry.org/ https://slack.cloudfoundry.org/, in the #buildpacks channel.

tzs 9y ago

One then that would have seriously helped me a few months ago, when I did a little project to learn some C# and write a command line tool using .NET Core would be a simple list of "using" statements that I'm likely to see in C# books and other documentation that are not available in Core (or that need configuration or settings changes to make work). (Or maybe the other way...a list of all "using" statements that work out of the box). The command line tool I was trying to write was to read my Safari reading list on my Mac, and construct an HTML page that contains the same information that I could put on my website, where I could then access it from my Surface Pro. Apple provides a way to export the reading list in XML, so that was my input. I don't remember what it was now, but my first approach used some XML stuff that I got out of examples from some recent C# book, and it worked fine in Visual Studio Community Edition on my Windows gaming machine. In Core, though, on my Mac (and on my Surface Pro and Windows gaming machine) it failed to build. It was not finding something I was trying to include via "using". I was not able to figure out if that thing is simply not part of Core, or if some build setting somewhere has to be changed to make it available. (I eventually changed my approach and dealt with the XML through LINQ instead of at a lower level, so that I no longer needed whatever it was whose "using" was giving me trouble, and successfully got access to my Reading List from my Surface Pro).