Thomas Malkewitz

I don't currently support updateable help, the only help comes with the module as an .xml file.

so, not sure what i want to to about this. I really would like to keep the cab file with the repo, but it appears that is not really possible...

i do UpperCaseEachWord for parameters for functions, and lowerCamelCase for variables inside functions.

I personally do it like this: ```powershell Get-Process | Sort-Object -Property Name | Out-GridView ``` When I'm writing scripts anyway. I don't do that when I'm using the shell.

dark theme that came in the spring? is that with the ISE preview thats in the gallery?

I have a good portion of this done now. but I cannot edit your orginal check list. still have to do: - Set-GitHubGist which will encompass the Star/unstar. - Delete...

lol, I forgot I already did the Remove-GitHubGist cmdlet, yesterday was a long day. I am going to tackle the rest of this today/tomorrow. Ill get to pesters too. One...

the easiest explanation would be to look at the repo. it just makes the deployment process easer, because only deliverable code exists in the root of the module. Basically there...

so, this seemed to be an issue with the example of port 8001, once I changed that, it works. Is there some way to maybe test for the port and...

I tried this: ``` PowerShell $text = "Hello world" $sb = $ExecutionContext.InvokeCommand.NewScriptBlock(@" $text "@) New-Flancy -url http://localhost:8002 -webschema @( Get "/" { $sb } ) ``` and when I go...