Merge pull request #101 from joeyaiello/JuneCommCall

Add June and July community call links/transcripts

Author: SteveL-MSFT

CommunityCall/20170615_ChatTranscript.txt

@@ -0,0 +1,195 @@
+Joey Aiello 9:31 AM: 
+Hey everyone!
+Joey Aiello 9:31 AM: 
+Just getting set up, give us a second
+Sullivan, Trevor 9:31 AM: 
+Hello
+Joey Aiello 9:32 AM: 
+Hello!
+Sullivan, Trevor 9:32 AM: 
+Yes
+Glenn Sarti 9:32 AM: 
+yup
+Darwin Sanoy 9:32 AM: 
+yes
+Iain Brighton 9:32 AM: 
+Yep!
+Keith Hill 9:32 AM: 
+yes
+Constantin Hager 9:32 AM: 
+jes
+Thomas Rayner 9:32 AM: 
+affirmative
+Constantin Hager 9:32 AM: 
+yes
+Monty Evans 9:32 AM: 
+yep
+Hector, Michael 9:32 AM: 
+(y)
+Eugene Bekker 9:37 AM: 
+Does the Job run with the environment captured of the launching environment?
+Keith Hill 9:40 AM: 
+Crytographically strong randomness one might say. :-)
+Steve Lee (POWERSHELL) 9:41 AM: 
+lol
+Glenn Sarti 9:41 AM: 
++1 UTF8NOBOM
+Thomas Rayner 9:42 AM: 
+That's awesome
+Keith Hill 9:44 AM: 
++1 for uniform experience cross-plat.
+Darwin Sanoy 9:44 AM: 
+This just effects PowerShell Core?
+Keith Hill 9:45 AM: 
+Unicode in-mem and UTF8 on file just makes sense.
+Sullivan, Trevor 9:45 AM: 
+Oh, so *that's* why VSCode kept saying that my module manifests were binaries. Interesting.
+Keith Hill 9:45 AM: 
+Yup
+Jonathan Medd 9:45 AM: 
+Yay for fixing that problem with New-ModuleManifest and git. I wondered why that happened :-)
+Keith Hill 9:45 AM: 
+Which BTW is why Plaster generates a module manifest as UTF8NoBOM.
+Nicholas M. Getchell 9:45 AM: 
+Thanks Keith! 
+Keith Hill 9:47 AM: 
+Hate to admit this but I didn't even know powershell.exe took positional params. I always specify -Command or -File
+Sullivan, Trevor 9:47 AM: 
+I always specify parameter names for the powershell binary, too.
+Eugene Bekker 9:48 AM: 
+Is it time to consider a distinct name for the PS Core binary vs Windows PS?
+Eugene Bekker 9:48 AM: 
+For example, leave WInPS as powershell.exe and something else, like ps1.exe or posh.exe
+Sullivan, Trevor 9:48 AM: 
+PowerShell Desktop Edition vs. PowerShell Core Edition @Eugene
+Eugene Bekker 9:48 AM: 
+for PS6+
+Glenn Sarti 9:49 AM: 
+I assume it'll throw an appropriate error (file not found) to the console if you do pass in a command instead of a file... Nothing too obtuse
+Keith Hill 9:49 AM: 
+RE & operator - so the job is a traditional out-of-proc job instead on an in-process (separate runspace) job?
+Eugene Bekker 9:50 AM: 
+Thanks @Trevor
+Eugene Bekker 9:50 AM: 
+Two different names means we can have both live side-by-side on Windows with no conflicts or ambiguity
+Sullivan, Trevor 9:51 AM: 
+There are bigger fish to fry than changing the PowerShell binary name. Just leave it for now.
+Keith Hill 9:51 AM: 
+You could do that with a version parameter, no?
+Eugene Bekker 9:51 AM: 
+If PS6 is changing the CLI params (which is great!), but it will mean invoking PS.exe will require some magic by the caller
+Eugene Bekker 9:52 AM: 
+Also, maybe with PS Core have the ability to specify which "Engine Version" is loaded, much like dotnet CLI allows multiple SDKs living side by side
+Keith Hill 9:52 AM: 
+Heh maybe powershell needs a version manager. :-) psvm select 6.1
+Eugene Bekker 9:52 AM: 
+:-)
+Sullivan, Trevor 9:52 AM: 
++1 Keith
+Glenn Sarti 9:52 AM: 
+Thanks. Sometimes PS errors can be a bit verbose but that looks good.
+Bergmeister, Christoph (Reigate) 9:53 AM: 
++1 Keith because this would be great for testing
+Sullivan, Trevor 9:54 AM: 
+Are these discussions / feedback being discussed openly, or just internally to Microsoft? If you could point us to public discussions on pros/cons of issues like PS version manager and the binary renaming issue, that would be useful.
+Andrew Bradley 9:54 AM: 
+Will there be a simple, recommended way to invoke PSCore cross-platform? E.g. if a build script in an open-source project must have predictable UTF8 output on Linux and Windows
+Thomas Rayner 9:54 AM: 
+(N) changing the name of the binary name
+(Y) adding a minver/maxver/requirever param or launching
+Thomas Rayner 9:55 AM: 
+imo
+Eugene Bekker 9:55 AM: 
+But Desktop and Core are different enough that when I simply say "powershell.exe" I would like to have some predictability
+Keith Hill 9:55 AM: 
+Speaking of breaking changes, I'd like to add the Unicode esc seq PR to the agenda (towards the end) if possible since it is a low risk breaking change. Would be nice to get into 6.0.
+Eugene Bekker 9:55 AM: 
+Especially if you're changing the CLI params
+Sullivan, Trevor 9:56 AM: 
+A *huge* issue to me is the lack of semantic versioning for dependencies in PowerShell module manifests. I'd love to see this breaking change in PS v6.0.
+Eugene Bekker 9:56 AM: 
+I agree -- it's not a "burning" issue
+Sullivan, Trevor 9:57 AM: 
+I hear you @Eugene. Nice to have, but pretty low in priority list.
+Thomas Rayner 9:59 AM: 
+Gotta run to another meeting. Thanks for the call and info!
+Joey Aiello 9:59 AM: 
+See ya! Thanks for joining! 
+Iain Brighton 10:01 AM: 
+Gotta shoot - thanks!
+Sullivan, Trevor 10:04 AM: 
+I had reported an issue with AssemblyLoadContext a couple calls ago ... does this fix that issue? I was getting a silent failure when loading a .NET Core assembly using the default load context.
+Sullivan, Trevor 10:05 AM: 
+I haven't tried on .NET Standard 2.0. Maybe I should give that a shot.
+Sullivan, Trevor 10:06 AM: 
+Wow, really? That is awesome. Single assembly for PS 3.0 Desktop *and* Core 6.0?
+Eugene Bekker 10:06 AM: 
+Awesome!  +1 PSStd
+David Jones 10:09 AM: 
+why not use install-package ?
+Sullivan, Trevor 10:09 AM: 
+Any news to share about including PowerShell Remoting "out of box" with the PowerShell Core install package? 
+Keith Hill 10:13 AM: 
+Here the two Unicode esc forms as implemented: fixed width "`u00A9Acme Inc" (ala C# and Bash) and variable width "`u{1f44d}" (ala JavaScript) that also supports Unicode surrogate pairs (emoji).
+Sullivan, Trevor 10:14 AM: 
+I already have an "Emojis" PowerShell module. :) 
+Sullivan, Trevor 10:14 AM: 
+It's on the PowerShell Gallery.
+Keith Hill 10:16 AM: 
+BTW big +1 to whoever fixed the PSReadline bug that was causing garbage characters to be displayed in the prompt on Linux.
+Bergmeister, Christoph (Reigate) 10:16 AM: 
+I find it great that you want to make PowerShell rather quality rather than date driven but can we have an update for each Beta version how many more Beta versions are roughly expected until RTM?
+Jonathan Medd 10:16 AM: 
+Can you join it now? I thought it was only recorded with the MS Azure guys?
+Sullivan, Trevor 10:16 AM: 
++1 Keith to PSReadline fix. Does that fix the issue with VSCode Integrated Terminal?
+Sullivan, Trevor 10:17 AM: 
+I used to get all sorts of weird characters printed in the Integrated Terminal, and it was rather unpredictable / hard to reproduce.
+Keith Hill 10:18 AM: 
+THere is a caveat to that fix. The last line which PSReadline modifies (changes color to indicate error) must not contain any vt term esc seqs.
+Nicholas M. Getchell 10:18 AM: 
+I saw that as well Trevor. I couldn't tell if it was PSReadline, vscode-powershell ext, integrated terminal, or my prompt. It was so random. 
+Sullivan, Trevor 10:18 AM: 
++1 for quality-driven release. Thanks for your efforts in this area. :)
+Sullivan, Trevor 10:19 AM: 
+@Nicholas yeah, I'm not sure where the source of the issue was. Figured Keith would know.
+Bergmeister, Christoph (Reigate) 10:19 AM: 
+Thanks for the info. :-)
+Sullivan, Trevor 10:19 AM: 
+I'm using VSCode on Mac.
+Sullivan, Trevor 10:20 AM: 
+It might have been PSReadLine related.
+Eugene Bekker 10:20 AM: 
+The link hasn't been posted yet
+Eugene Bekker 10:20 AM: 
+According to Roney's twitter
+Sullivan, Trevor 10:20 AM: 
+Have a great day folks, cheers!
+Bergmeister, Christoph (Reigate) 10:21 AM: 
+I found some minor remoting bugs for older pre-release version of PowerShell and OpenSSH. They are not blocking for me but are you still interest in getting to know about them?
+Keith Hill 10:21 AM: 
+@trevor - https://github.com/lzybkr/PSReadLine/issues/470
+Keith Hill 10:21 AM: 
+Chrome is slow!!
+Glenn Sarti 10:22 AM: 
+Thanks all!
+Darwin Sanoy 10:22 AM: 
+Memory hog cause it follows UAC process level best practice - like IE ;)
+Keith Hill 10:22 AM: 
+Thanks!
+Darwin Sanoy 10:22 AM: 
+THanks!
+Eugene Bekker 10:22 AM: 
+Thanks!
+Kenny, Richard 10:22 AM: 
+Thanks
+Hector, Michael 10:23 AM: 
+TY
+Jonathan Medd 10:23 AM: 
+Thanks
+Bergmeister, Christoph (Reigate) 10:23 AM: 
+Thanks
+Wiedmeyer, Martin - NTT 10:23 AM: 
+demke
+Joey Aiello 10:24 AM: 
+bitte

CommunityCall/20170720_ChatTranscript.txt

@@ -0,0 +1,168 @@
+Sullivan, Trevor 9:30 AM: 
+You sound fine
+Kurt Roggen [BE] 9:31 AM: 
+:-)
+Glenn Sarti 9:31 AM: 
+Ya for swag!
+Sullivan, Trevor 9:33 AM: 
+#WhoNeedsBackups
+Simon Wåhlin 9:33 AM: 
+What backup? #ItAllinTheCloud :D
+Sullivan, Trevor 9:33 AM: 
+#LivingOnTheEdge 
+Joey Aiello 9:33 AM: 
+https://blogs.msdn.microsoft.com/powershell/2017/07/14/powershell-6-0-roadmap-coreclr-backwards-compatibility-and-more/ 
+Keith Hill 9:36 AM: 
+The blog post says you are using .NET Standard 2.0. Is that really true? I thought you were actually targeting NetCoreApp2.0 / net4xx?
+Sullivan, Trevor 9:37 AM: 
+I always install the latest beta as soon as it's available. :) Keeps getting better.
+Keith Hill 9:37 AM: 
+Are you sharing?
+Keith Hill 9:37 AM: 
+Are you sharing?
+Sullivan, Trevor 9:37 AM: 
+I don't see anything sharing.
+Kurt Roggen [BE] 9:39 AM: 
+Loading...
+Keith Hill 9:41 AM: 
+RE: solve dev story in beta5/6 - thank you!
+Kurt Roggen [BE] 9:43 AM: 
+compatibility assistant
+Sullivan, Trevor 9:44 AM: 
+Any news around dependency management going forward?
+Darwin Sanoy 9:46 AM: 
+Ok it's actually LuaBugLight by Aaron Margosis.  I don't mean that the tool code could be reused - but the concept: https://blogs.msdn.microsoft.com/aaron_margosis/2015/06/30/lua-buglight-2-3-with-support-for-windows-8-1-and-windows-10/ 
+Glenn Sarti 9:46 AM: 
+Not sure if this is RFC worthy....is there any way to a "registry" of installed PS versions on a host. Give we can install PS6 pretty much anywhere, how could we discover where PS is installed on the filesystem (and potentially version)
+Darwin Sanoy 9:48 AM: 
+Glenn: https://blogs.msdn.microsoft.com/aaron_margosis/2015/06/30/lua-buglight-2-3-with-support-for-windows-8-1-and-windows-10/ 
+Sullivan, Trevor 9:48 AM: 
+One thing I'd love some team / community help on ... writing native cmdlets for Mac OS X and Linux. Some examples of how to call native libraries would be awesome.
+Darwin Sanoy 9:49 AM: 
+Glenn: dir 'C:\Program Files\powershell\*\powershell.exe' | %{ get-command $_.fullname} 
+Glenn Sarti 9:49 AM: 
+reworded: Not sure if this is RFC worthy....is there any way to a "register" an installed PS versions on a host. Given we can install PS6 pretty much anywhere, how could we discover where PS is installed on the filesystem (and potentially version)
+Glenn Sarti 9:49 AM: 
+Does PS _have_ to be installed there is it just default?
+Devin 9:49 AM: 
+Seems like having env variable aware .net targetting and stuff might be best in an IDE
+Devin 9:50 AM: 
+but w/e
+Joel Bennett 9:50 AM: 
+Can we talk about the plan for ACTUALLY supporting .Net Standard 2 for nuget packages?
+Darwin Sanoy 9:51 AM: 
+I'd vote environment variable too because it would work multiplatform
+Keith Hill 9:55 AM: 
+Dumb question - can't PS just use nuget.exe to resolve nuget dependencies?
+Keith Hill 9:55 AM: 
+Hehe - that was me Joel. PSake required VSSetup on Windows but not needed on Linux/macOS.
+Devin 9:59 AM: 
+So would this be a requires that can target OS?
+Devin 9:59 AM: 
+and exclude OS
+Devin 9:59 AM: 
+?
+Joel Bennett 9:59 AM: 
+yes please ;-)
+Darwin Sanoy 10:00 AM: 
+This conversation is being had in the Chocolatey community as well.
+Simon Wåhlin 10:00 AM: 
+Sounds like something along the line of what Warren Frame is doing in PSDepend doesnt it?
+Jeff Dean 10:00 AM: 
+Not really related to dependencies, but does Core already support Desired State Configuration declarative 'function' types?
+Darwin Sanoy 10:00 AM: 
+Richer dependency and requirements declaration in .nuspec
+Keith Hill 10:02 AM: 
+@Trevor - isn't that a .NET Core platform invoke call to a native shared lib?
+Keith Hill 10:02 AM: 
+So sprinkle in some C# code with a pinvoke call.
+Sullivan, Trevor 10:02 AM: 
+@Keith: Possibly, yeah. I just am not familiar with native libraries on non-Windows platforms.
+Keith Hill 10:02 AM: 
+It's not that hard.
+Keith Hill 10:03 AM: 
+Example:
+[DllImport("libc")]
+static extern int read(int handle, byte[] buf, int n);
+Steve Lee (POWERSHELL) 10:04 AM: 
+https://github.com/PowerShell/PowerShell/tree/master/src/libpsl-native 
+Keith Hill 10:04 AM: 
+That's a C# sample but that could be Add-Type'd
+Keith Hill 10:04 AM: 
++1
+Steve Lee (POWERSHELL) 10:04 AM: 
+https://github.com/PowerShell/PowerShell/blob/master/src/System.Management.Automation/CoreCLR/CorePsPlatform.cs 
+Sullivan, Trevor 10:04 AM: 
+@Keith: nice. I think the big things is needing docs for native libs.
+Keith Hill 10:05 AM: 
+Yup.
+Glenn Sarti 10:05 AM: 
+Joey: thanks for that. More thinking to do.
+Joel Bennett 10:06 AM: 
+It will depend how much you break
+Glenn Sarti 10:06 AM: 
+hahah...yeah right
+Joey Aiello 10:06 AM: 
+https://github.com/PowerShell/PowerShell-RFC/pull/97 
+10:07 AM This message wasn't sent to Kexy Biscuit.
+https://github.com/PowerShell/PowerShell-RFC/pull/97 
+Devin 10:08 AM: 
+Skip it :)
+Devin 10:08 AM: 
+Ty
+Bobby Cannon 10:12 AM: 
+I think that is the Core expectation? Correct?
+Keith Hill 10:12 AM: 
+--self-contained. :-)
+Sullivan, Trevor 10:12 AM: 
+Hopping off the call. Cheers for the help, guys!
+Darwin Sanoy 10:13 AM: 
+powershell-core is on chocolatey - but does not show up due to being marked beta
+Darwin Sanoy 10:14 AM: 
+If we can decide an environment variable pointer name for "current version of core" I can add it to the chocolatey package
+Darwin Sanoy 10:15 AM: 
+This variable would be helpful for making powershell core the default CLI for openssh
+Bobby Cannon 10:17 AM: 
+I haven't done any research on this but since you guys are talking about it. I create a custom application that is a PowerShell host / terminal. Would I want to host PowerShell 6 in process or find PowerShell in the environment and communicate with it via PowerShell Editor Services?
+Joel Bennett 10:18 AM: 
+What they just told me is that right now the only way is to host PS6 and ship all of it with your host app.
+Jeff Dean 10:18 AM: 
+correct
+Bobby Cannon 10:19 AM: 
+ok, sounds good. Core is new, can I host 6 in .NET 4.6.2?
+Bobby Cannon 10:19 AM: 
+new to me that is...
+Jeff Dean 10:19 AM: 
+that leads to the question... will the LCM eventually support PS core 6?
+Jeff Dean 10:21 AM: 
+ty
+Keith Hill 10:28 AM: 
+Looking through gh/ps/docs and not finding a doc on creating a cross-platform binary module? Anyone have a link to such a doc? Or is the host-powershell.md the doc?
+Keith Hill 10:29 AM: 
+k, just wondering when to start messing with this - after having been burned by net core 1.0 alphas :-)
+Keith Hill 10:29 AM: 
+Does seem to be firming up. New msbuild rocks.
+Keith Hill 10:30 AM: 
+Thanks!
+Nicholas M. Getchell 10:30 AM: 
+Thanks
+Thomas Rayner 10:30 AM: 
+Thanks guys!
+Glenn Sarti 10:30 AM: 
+thanks all
+Darwin Sanoy 10:30 AM: 
+Thanks for doing these calls!
+Jeremiah Strong 10:30 AM: 
+Always enjoy hearing the latest; thx for doing this
+Joel Bennett 10:30 AM: 
+Y’all rock :-)
+Simon Wåhlin 10:30 AM: 
+Thanks alot! 
+Joel Bennett 10:30 AM: 
+lol
+Devin 10:30 AM: 
+bai
+Darwin Sanoy 10:30 AM: 
+bye
+Jonathan Medd 10:30 AM: 
+Thanks