When I worked at the gas station I saw this all the time.
Jiggly blondes or people that ripped the pump off?
When I worked at the gas station I saw this all the time.
Both. I worked in the ghetto and there was plenty of T/A everywhere.Jiggly blondes or people that ripped the pump off?
I guess we are spoiled over here when it comes to readily available BBQ sauces. Sweet baby Ray's is good, but so are many others. Sticky Fingers has some good sauces; I am partial to the Sweet Southern Heat and Memphis Original. Bull's-Eye is good, as is Stubb's and KC Masterpeice. Bot the best is what you make yourself, hands down.
I guess we are spoiled over here when it comes to readily available BBQ sauces. Sweet baby Ray's is good, but so are many others. Sticky Fingers has some good sauces; I am partial to the Sweet Southern Heat and Memphis Original. Bull's-Eye is good, as is Stubb's and KC Masterpeice. Bot the best is what you make yourself, hands down.
Does anyone here understand Runspaces/threading and sync hashing in PowerShell ? I tried to incorporate it into my code using the Foxdeploy guide. But the guide is not detailed, doesn't explain much of anything. It took hours of wrangling just to get the GUI to show up (I am using PowerShell backend on a XAML based Windows Form made in Visual Studio, turns out it didn't like part of the Window declaration in the XAML code.. but I digress). But, the GUI does nothing. It doesn't interact with all the actual script logic behind it, which is placed in a seperate runspace. I copy and paste the sample code and it all works fine, but I swap and place my code in it's place within the sample code (keeping the hashing/runspaces in place) and it just doesn't work.
I kinda need to figure it out, because atm my powershell logic code is about 500 lines long and full of loops and a fair bit of waiting for objects to sycnhronize to Azure/O365. It works fine without threading it and using different runspaces, but the whole GUI freezes while the script block executes after clicking the button.
halp plz.
I've done BackgroundWorker threads in C# to not freeze GUI's while background processing is being done. Not sure if that really helps though, because I don't do much with PowerShell . Just straight .NET / C#.
function Write-FormHost {
param( [string]$Text )
$Form.Dispatcher.Invoke(
[action]{$WPFStatusTextBlock.AddText("$($Text)`n")},
"Render"
)
}