|
If he makes me accidentally pick up some Dutch I'm blaming you.
To err is human. Fortune favors the monsters.
|
|
|
|
|
You invented 'comments' in serial communication, don't you?
"In testa che avete, Signor di Ceprano?"
-- Rigoletto
|
|
|
|
|
Nice work!
It reminds me the Amiga Diagnostic ROM, that sends everything both to the screen and to the serial port - in case the screen actually totally toasted...
“Real stupidity beats artificial intelligence every time.”
― Terry Pratchett, Hogfather
|
|
|
|
|
Wordle 378 4/6
⬜⬜⬜🟩⬜
⬜⬜🟨🟩🟩
🟨🟨⬜🟩🟩
🟩🟩🟩🟩🟩
|
|
|
|
|
|
Wordle 378 5/6
⬜⬜⬜⬜🟨
⬜⬜🟩🟨⬜
⬜⬜⬜⬜⬜
⬜🟨🟩🟩🟩
🟩🟩🟩🟩🟩
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
Wordle 378 4/6
🟨⬜⬜🟩⬜
⬜⬜🟨🟩⬜
🟨🟨🟨🟩🟩
🟩🟩🟩🟩🟩 Not a wrod I use much in general conversation, but ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
If it's 12345, then 312345 is more useful!
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Wordle 378 3/6*
🟨⬜⬜⬜🟩
⬜🟨🟨🟩🟩
🟩🟩🟩🟩🟩
Happiness will never come to those who fail to appreciate what they already have. -Anon
|
|
|
|
|
Wordle 378 4/6
⬜⬜⬜🟩🟨
🟨🟨⬜🟩🟩
🟨🟨🟨🟩🟩
🟩🟩🟩🟩🟩
Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
|
Wordle 378 4/6
⬛🟨⬛🟨🟨
🟨🟨🟨⬛⬛
🟨🟨🟨⬛⬛
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 378 5/6
⬛⬛⬛🟨🟨
⬛🟨⬛🟩🟨
🟨🟨🟨🟩⬛
🟨🟨⬛🟩🟩
🟩🟩🟩🟩🟩
Get me coffee and no one gets hurt!
|
|
|
|
|
Wordle 378 4/6
⬛🟨⬛⬛🟨
🟨🟨⬛⬛⬛
⬛⬛⬛⬛🟨
🟩🟩🟩🟩🟩
|
|
|
|
|
still can't get wordle to post my results to here. cut and paste did not work either.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
I am starting to learn PowerShell. I have avoided it for years, because whatever I needed to do beyond a simple BAT file, I could do in C#.
However, I am in a situation where I have to use PowerShell, so I am learning it.
One of the things I learned is that within a PowerShell script, you can call .cs files to run C# code. So this question came to mind, and I thought you all might have some opinions. I wrote a PS script that calls a .cs file and does exactly what I described. I have not mastered calling non-GAC .NET library DLLs yet, but I am working on it.
Why not use PowerShell as a management script, and write C# code to execute the "business logic"? I am not convinced that it is better to use PowerShell cmdlets to hack up some brittle script to do what can be more easily done in C#, which is far more capable and wider-ranging than PowerShell script.
This is a snippet from my script:
$Source = Get-Content "SomeCSClass.cs" -Raw
Add-Type -TypeDefinition $Source
$TestDLL = New-Object PSTest.SomeCSClass
$TestFilePath = $TestDLL.GetCurrentDirectory() + "\PowerShell Example Files\"
## Get a list of files using C# code from a static method
$Files = [PSTest.SomeCSClass]::GetListOfFiles($TestFilePath, "*.txt", 0)
Your thoughts?
|
|
|
|
|
I also avoid PowerShell, it's of no use to me either.
|
|
|
|
|
This is very welcome news. I might just want to learn PowerShell after all just for this capability.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Powershell+C#=cryptic^2
sorry no interest
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
Cryptic only if you are not familiar with C#. For someone who is used to the 40+ year old approach of scripting shells, they might find it easier to stay with scripting.
And if you don’t have to use scripting shells - don’t. It is a backwards way to get work done. But, in my case, I have no choice. Trying to convince a DevOps team they do not need scripting is a lost cause.
|
|
|
|
|
I tried PowerShell a couple of times, but I agree that for a C# programmer the syntax is really awful.
modified 11-Nov-22 12:51pm.
|
|
|
|
|
Years ago I wrote a C# DLL that allows my programs to take in raw C# cs files and run them as scripts.
Why PowerShell was created without the ability to natively use C# for scripting instead of that inane verb-noun syntax with the cryptic parameters is beyond me.
|
|
|
|
|
If all your business logic is C#, and you just read it in PS, you can't step through that code to debug it. Of course if that's already been thoroughly tested and you're dropping it in as-is, then it's not much of an issue.
PS can create/use the same .NET objects you're familiar with natively. Yes, the syntax can be non-intuitive at first, but once you get the hang on it, the benefit of being able to bang out a short script to automate some menial task beats having to fire up VS and build/compile an EXE every time you want to make a tiny change.
|
|
|
|
|
PS syntax is not intuitive. It is awful to work with.
What I do is create a C# library DLL project, and write unit tests for the class(es). Then I include my ps1 file, which I can run from within VS by using the PS ISE, which loads the cs file.
That gives me good source control, good testing, and minimal “script kiddie” coding.
C# is far more versatile and elegant with which to code. Since our team standardized on PS long before I got there (DevOps stuff), it then is compatible with what others are doing by staying within the PS world.
|
|
|
|
|
MSBassSinger wrote: C# is far more versatile and elegant with which to code
Well obviously. PS and C# serve completely different purposes.
|
|
|
|