Hold my beer, gonna get popcorn for the show! :-\

Rules for the FOSW ![^]

MessageBox.Show(!string.IsNullOrWhiteSpace(_signature)
? $"This is my signature:{Environment.NewLine}{_signature}": "404-Signature not found");

Thanks mate... X|

______________________
// \\
| (X) NEW FEAR UNLOCKED |
\\______________________//

Rules for the FOSW ![^]

MessageBox.Show(!string.IsNullOrWhiteSpace(_signature)
? $"This is my signature:{Environment.NewLine}{_signature}": "404-Signature not found");

(20. Juni 2024) 4/6 ⬛🟨⬛⬛⬛ 🟨🟩⬛⬛⬛ 🟩🟩🟩⬛🟩 🟩🟩🟩🟩🟩

Rules for the FOSW ![^]

MessageBox.Show(!string.IsNullOrWhiteSpace(_signature)
? $"This is my signature:{Environment.NewLine}{_signature}": "404-Signature not found");

Happy Boopday! Enjoy it, have a drink. All the best wishes!:java:

Rules for the FOSW ![^]

MessageBox.Show(!string.IsNullOrWhiteSpace(_signature)
? $"This is my signature:{Environment.NewLine}{_signature}": "404-Signature not found");

(12. Juni 2024) 5/6 ⬛⬛⬛🟨⬛ ⬛🟩🟨⬛🟩 ⬛🟩⬛🟨🟩 🟩🟩⬛⬛🟩 🟩🟩🟩🟩🟩

Rules for the FOSW ![^]

MessageBox.Show(!string.IsNullOrWhiteSpace(_signature)
? $"This is my signature:{Environment.NewLine}{_signature}": "404-Signature not found");

Plus, if each Pixel costs 10 cents you'll be rich ... :suss:

Rules for the FOSW ![^]

MessageBox.Show(!string.IsNullOrWhiteSpace(_signature)
? $"This is my signature:{Environment.NewLine}{_signature}": "404-Signature not found");

(5. Juni 2024) 4/6 ⬛🟨⬛🟨⬛ ⬛⬛🟨⬛🟨 ⬛🟩⬛🟩🟩 🟩🟩🟩🟩🟩

Rules for the FOSW ![^]

MessageBox.Show(!string.IsNullOrWhiteSpace(_signature)
? $"This is my signature:{Environment.NewLine}{_signature}": "404-Signature not found");

jschell wrote:

As described all of those currently exist without customization. One might also wonder if this custom stuff is secure. Specifically how is be being tested to insure that it is secure and will remain so.

Yep... Uhm ... exactly one of the first things i was asking when i heard that, on the plus side i was able to read the whole BLE traffic with a sniffer when i was asked to measure and verify time needed for updates over ble.

jschell wrote:

Windows 10 runs on 64 bit systems but it also runs on 32 bit systems.

Yep, i should have mentioned we need both.

jschell wrote:

Presumably the company at least has the source code. And yes there are risks to the company in not insuring continuity in case there are problems.

:~ I am also asking the question because i want to ensure that we will not be screwed if something funny happens. All the info will be used to lay out a plan and strategy to not fall off the edge.

Rules for the FOSW ![^]

MessageBox.Show(!string.IsNullOrWhiteSpace(_signature)
? $"This is my signature:{Environment.NewLine}{_signature}": "404-Signature not found");

Thanks, i may need that :~ To answer your first statement, it is required for us to support 64bit and 32Bit, with .NET it's easy -> Compile for Any CPU and done. I know it's more complicated in C++.

Rules for the FOSW ![^]

MessageBox.Show(!string.IsNullOrWhiteSpace(_signature)
? $"This is my signature:{Environment.NewLine}{_signature}": "404-Signature not found");

Thanks for that. Yep, i just started there quite fresh as well but it seems i am, because of the tasks i was assigned to, the one that finally starts to clean up some old things. And yes, it'll be fun if something unexpected happens. I'll keep the last bit in mind and will address this task to my superior.

Rules for the FOSW ![^]

MessageBox.Show(!string.IsNullOrWhiteSpace(_signature)
? $"This is my signature:{Environment.NewLine}{_signature}": "404-Signature not found");

Oh yeah, the room of boxes... Don'T remind me about that, mine needs cleaning and reorganization as well...

Rules for the FOSW ![^]

MessageBox.Show(!string.IsNullOrWhiteSpace(_signature)
? $"This is my signature:{Environment.NewLine}{_signature}": "404-Signature not found");

Thanks for the answers, that lit up some dark corners for me. His proposal is to do simply convert the necessery stuff for 64 bit aswell so he'll provide both for us, not changing or modernizing anything. That's what i would have guessed, an example given, we have code for BLE communication in such a library, i know that Microsoft API or respectivly .NET has a lot of Code and Features provided for BLE communication. SO my idea was, since he knows both worlds, to take the effort and convert to .NET, at least the things that are possible, he wasn't happy... No, i hope i mentioned it but our application is bound to another external application that standardises things. Therefore we are only supporting Win 10 and 11 because said "Frame Application" is only running on those two. Thanks again for your answer :)

Rules for the FOSW ![^]

MessageBox.Show(!string.IsNullOrWhiteSpace(_signature)
? $"This is my signature:{Environment.NewLine}{_signature}": "404-Signature not found");

Germany the same, you have a socket, cable runs vert or hori, but some brilliant folks doing this the first will always do it wrong. I even found these old cable loops where someone didn't want to use proper cable extension material and just removed the isolation, looped it around a nail or screw and then hung the other cable in the exact same way on the nail or screw... X|

Rules for the FOSW ![^]

MessageBox.Show(!string.IsNullOrWhiteSpace(_signature)
? $"This is my signature:{Environment.NewLine}{_signature}": "404-Signature not found");

I mean, if you had tried to hit the center you would never have gotten it. But yep, that's exactly the reason why i bought mine, so i can find metal, wood, and electricity. Never failed me so far.

Rules for the FOSW ![^]

MessageBox.Show(!string.IsNullOrWhiteSpace(_signature)
? $"This is my signature:{Environment.NewLine}{_signature}": "404-Signature not found");

And while we are at drilling anyway, always check that where you drill there is nothing behind your planned hole. Wouldn't be the first time that someone either tears the power cables apart or even worse, flushes his room with the water from the pipes :rolleyes:

Rules for the FOSW ![^]

MessageBox.Show(!string.IsNullOrWhiteSpace(_signature)
? $"This is my signature:{Environment.NewLine}{_signature}": "404-Signature not found");

Congrats on being an inventor! I hope it serves you well :)

Rules for the FOSW ![^]

MessageBox.Show(!string.IsNullOrWhiteSpace(_signature)
? $"This is my signature:{Environment.NewLine}{_signature}": "404-Signature not found");

If you do DIY right it's rewarding, if you get screwed up by tools and products you use it's annoying. End of the story. "Pro tip" from my side, never use anything provided with the product and instead have dowels and screws in your toolbox that are good quality.

Rules for the FOSW ![^]

MessageBox.Show(!string.IsNullOrWhiteSpace(_signature)
? $"This is my signature:{Environment.NewLine}{_signature}": "404-Signature not found");

Hi there, i have a question regarding C++ "language updates", to phrase properly what i want to know: We currently have an external employee that codes C++ Libraries for us, which are used for "drivers" to ensure communication via Ethernet, USB and Bluetooth. Those libraries are currently only available as 32 Bit dll's and therefore created a discussion after we found out that in some cases we would as well need them as 64 Bit. To get to the point, said collegue also mentioned, that those libraries are ensuring a downwards compatibility to run on systems below windows 10 (which is our current limit of support), namingly they run even on Windows XP and probably further down, written with VS 2005 iirc. Since i am .NET developer i can not really grab the necessity for doing so, nor estimate the potential "risks, flaws or performance" related topics comming up with that compatibility. So i want to ask you if my concerns are correct or totally wrong, when it comes to using "very old" C++ instead of modernizing it and only ensuring runtime compatibility to "current" OS'es. I personally feel that, since C++ get's updated every now and then, there must be a reason for doing so, as well as ofc improving the final produce that get's spit out by the compiler if your using newer (not newest) C++ Versions. As a bonus, if someone could take the time to answer this as well, would you suggest, think about or deny switching code parts into C# and .NET which probably could be switched due to framework functionalities where we can rely on the stuff microsoft already has built in there? As a note: We leave aside the fact that nobody else from the team would have hardware to continue coding or even compile this old stuff. In any case, thanks alot for reading and / or answering.

Rules for the FOSW ![^]

MessageBox.Show(!string.IsNullOrWhiteSpace(_signature)
? $"This is my signature:{Environment.NewLine}{_signature}": "404-Signature not found");

Exactly... well now i am really confused, my testing app is 4.7.2 but the version info of the official application is .NET 4.0.3. So additionally to not knowing 100% how all of that stuff works i even don't know how this specific works out! *edit* My Test app as well looks like .NET 4.0.3 or am i just dumb today?

Console output:

DeviceModel: .NET Version 4.0.30319.42000 'TestApp.exe' (CLR v4.0.30319:TestApp.exe): Loaded 'C:\ProgramData\...\Device.dll'.

Rules for the FOSW ![^]

MessageBox.Show(!string.IsNullOrWhiteSpace(_signature)
? $"This is my signature:{Environment.NewLine}{_signature}": "404-Signature not found");

(8. Mai 2024) 5/6 🟨⬛⬛🟩🟩 ⬛🟩🟩🟩🟩 ⬛🟩🟩🟩🟩 ⬛🟩🟩🟩🟩 🟩🟩🟩🟩🟩 Brain.exe was offline today...

Rules for the FOSW ![^]

MessageBox.Show(!string.IsNullOrWhiteSpace(_signature)
? $"This is my signature:{Environment.NewLine}{_signature}": "404-Signature not found");