Alison Perez
Alison Perez
@Asherslab this just reuses the command path and arguments, it doesn't reuse the same instance of the init application. In the example I gave, showing both CPU load and RAM...
@drozdowsky: for my example of database connections, I did exactly that. I spent a half hour yesterday throwing together a windows service that responds to simple commands over the network....
That would probably work for my use case, but the current behavior isn't a huge issue. Just means waiting a moment for the data to shift.
That did get brought up, @kjnilsson asked if I could post this here anyway because it looks like vim's `system()` function runs things in the background as desired. Don't know...
Came here looking for something else and noticed @TheJayMann had linked my test branch. It's been ages since I touched that branch, so I'm not sure how well I had...
Stripped out all of my compiled binaries and left out the sample application I mentioned (internal application from work), and put what was left here: https://github.com/amazingant/FsXamlAgain
Coincidentally, I ran into this yesterday as well while trying to see if I could migrate a work project to .NET Core. Seems that this is related to the fact...
I'm not new to publishing .NET Core projects, but the project in question has quite a bit of workflow around it that requires the executable to be packaged the same...
I was able to locally modify Paket enough to bypass this issue by commenting out [these two lines](https://github.com/fsprojects/Paket/blob/cc3eaf42dd154344ff02cbf035068831946bdf5a/src/Paket.Core/Packaging/PackageProcess.fs#L29-L30), removing associated code that used the values, and adding the missing data...