|
All I know is it worked on my Surface 3 Pro (to my external drives), and it works on my Go 2 (to the SD card).
And I got to order a cable. 
"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!
|
|
|
|
|
Do you have Bitlocker enabled on the Surface ?
"I didn't mention the bats - he'd see them soon enough" - Hunter S Thompson - RIP
|
|
|
|
|
No.
It's probably a plot to get you to buy a Surface Duo. I just got an email suggesting I did - starting at £1,300!
Good grief: you can buy a low end iPhone for that! 
"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!
|
|
|
|
|
Yes I got an email today about that
"I didn't mention the bats - he'd see them soon enough" - Hunter S Thompson - RIP
|
|
|
|
|
@petepjksolutionscom
Where's the CCC?
"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!
|
|
|
|
|
624 files, 52 folders, and 170mb of disk space - what a piece of crap.
The very same code written against .Net framework is only 3 files, and under 100k.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Yeah,
I can say the same thing about modern operating systems. I'm only using about 20% of the features in my operating system and have no use for most of the rest. Seems like every year the operating system gets bigger. Some of the features should be made modular for easy removal.
I can say the same thing about the C++ language... I have no use for many of the recent additions. Seems to be human–nature that we keep building larger.
Best Wishes,
-David Delaune
|
|
|
|
|
Randor wrote: Seems to be human–nature that we keep building larger.
Or at least the nature of Complex Adaptive Systems[^]
They tend to crop up when enough agents (like human hands, but not limited to human activity) enter a system to make it "take on a life of its own" - be it governments, economies, ecosystems, large software projects, etc.
They are adaptive which means they tend to "defend themselves" in a manner of speaking, and that tends to lead to growth, inasmuch as they are successful at thwarting attempts to curtail them. In that way they are much like any living thing.
All of this happens through these agents, but the individual behavior of the agents themselves doesn't determine the behavior of the system as a whole. A CAS is a kind of non-linear dynamical system so its inputs don't directly correlate with its outputs.
Fascinating stuff, really. Or maybe I'm just a nerd. 
Real programmers use butterflies
|
|
|
|
|
honey the codewitch wrote: the individual behavior of the agents themselves doesn't determine the behavior of the system as a whole.
Yep, this applies to the system you described.
honey the codewitch wrote: Fascinating stuff, really. Or maybe I'm just a nerd.
The Pareto principle[^] is absolutely real. I've seen the data myself when applied to > 120,000 global employees. I've also seen it applied to millions of customers and it was interesting to see that 20% of the customers were generating 80% of the support calls.
The WG21 committee is a small group of people steering the C++ language. Likewise there are only about ~200 or so program managers generating operating system features.
Anyway I get your point. 
|
|
|
|
|
Quote: The WG21 committee is a small group of people steering the C++ language. Likewise there are only about ~200 or so program managers generating operating system features.
Both of those statements explain a lot.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
Randor wrote: Seems like every year the operating system gets bigger. Some of the features should be made modular for easy removal.
The irony is that MS has spent a lot of time and effort refactoring Windows and making it more modular, and according to them, it's now as modular as it's ever been.
Of course, that doesn't translate into us end users being able to remove the crap we don't need...
|
|
|
|
|
I recall talk many years ago about modularizing Windows, and allowing users to add and remove components. Now, with the Windows store, MS is in a position to be able to do exactly that, but I don't get the impression they even remember those old ideas! (Or maybe I remember incorrectly! That is a possibility, too!)
|
|
|
|
|
You know, there's a MINIX for you.
"In testa che avete, Signor di Ceprano?"
-- Rigoletto
|
|
|
|
|
Compare that to Delphi 3.
Bastard Programmer from Hell 
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
modified 27-Mar-21 21:01pm.
|
|
|
|
|
It's because you deploy a self contained project!
You can trim it as small as before by deploying a framework dependent version. Checkout your publish settings!
|
|
|
|
|
I found out why it was doing that. I needed access to InstalledFontCollection, which is accessed with a reference to System.Drawing (the System.Drawing.Text namespace).
When I converted the app to .Net 5, I added the NuGet package Microsoft.Windows.Compatibility (on Microsoft's recommendation), which adds the 600+ files to the compiled project, and there's apparently no (easy or reasonable) way to relieve yourself of that payload.
WTF was Microsoft thinking?
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Were you using PrivateFontCollection ? I still don't see why it would be that much bigger as the standard framework would still need to access System.Drawing.Text
Edit
Sorry I didn't read your post thoroughly enough it's this bugger Microsoft.Windows.Compatibility
"I didn't mention the bats - he'd see them soon enough" - Hunter S Thompson - RIP
modified 18-Feb-21 7:01am.
|
|
|
|
|
Adding the cited package doesn't let you cherry pick what gets included in the compiled image. The solution (for my situation) was to uninstall that package, and all System.Drawing.Common to the project.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
How often is it that we run into a situation where we have a lot of backend or supporting code to write, and the client can see no progress?
I try to code around that, and break up those tasks so I can continue to show visible progress, probably drilled into me from the dotcom days always having to keep the venture capitalists happy with what we were creating.
But sometimes it's just not possible, especially when you're in a situation coding as a one person team developing way above your individual weight class, so to speak. Add that to developing two things that have to talk to each other wirelessly in the same language, on entirely different platforms.
Hence the title of this post, with apologies to Douglas Adams.
It can be a difficult situation, helping a client manage expectations. It really helps if you've shown a lot of progress early on and built some trust in the direction of the project with the client, but at the end of the day, it's ultimately about trust and client education, I've found. The more they know about the process of developing a product, the more likely they are to accept periods of it going "dark" in terms of visible advancement.
Still I prefer to keep these periods as short as possible and as rare as possible, because otherwise I myself get uncomfortable with the project. Spending too long in the weeds can make me lose sight of where I'm headed so as much as it's frustrating sometimes having to play show and tell every week it at least keeps me grounded.
Real programmers use butterflies
modified 17-Feb-21 17:58pm.
|
|
|
|
|
honey the codewitch wrote: It can be a difficult situation, helping a client manage expectations.
No, it ain't. It need to be done.
You don't ask a doctor to manage expectations. He/she tells you how it is and you learn to cope.
honey the codewitch wrote: It can be a difficult situation, helping a client manage expectations. It really helps if you've shown a lot of progress early on and built some trust in the direction of the project with the client, but at the end of the day, it's ultimately about trust and client education, I've found.
"We did the heart, now working on an unpredictable liver".
What progress I make is not part of a progress bar. Sometimes it very quick, some days me very slow. Like a Windows progressbar!
honey the codewitch wrote: show and tell every week it at least keeps me grounded.
Ehr, once a week? We do daily. And some days, nothing changes really, you just throw away a lot of code.
Bastard Programmer from Hell
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
I find it useful to use anything from a simple todo list in notepad to a ticketing system (pick your poison) where I break down all the back-end pieces that need to be implemented, individually tested, and then integration tested, for that one simple "see, clicking on the button works!" 30 second demo.
That way I can keep my own focus, add things as I realize "oh yeah, that needs to be done too" and "oh yeah, that scenario / edge case needs to be tested as well", and, assuming whatever you're using to mark each step along the way as "done", the client can see the progress you're making.
And of course, there's the brain chemistry[^] associated with motivation to work on a task and then marking it as done!
|
|
|
|
|
I lose notes, or can't interpret them later, so I use // TODO: statements in my code. Visual Studio produces a task list out of them. The other advantage is I (usually) know right where my TODO needs to happen.
Real programmers use butterflies
|
|
|
|
|
I run into that - a lot. I do the UI's for our products. The main product line uses C# and WPF. I've found it's easier to prototype directly in the product and demonstrate how it works than to draw a bunch of static pictures.
Fortunately the 'client' is the rest of the R&D team on the product, along with service, sales, and occasionally training. All of them understand that the pretty face is about 0.1% of the solution.
Software Zen: delete this;
|
|
|
|
|
I do similar except i mock using winforms for gui stuff because i hate the wpf designers, and i prefer designers for RAD UI development where possible. In fact winforms is great for me the way i code because it generates code and can roundtrip from the designer so i get both methods. WPF you can do it too, but the tags are annoying, and that's what the designer generates. Plus the designer itself is near impossible to use IMO.
So i dev in winforms for the mock, separating most of the actual logic, and them port it into WPF for the final product, which can then be tweaked but all the major elements and overall flow is there.
Real programmers use butterflies
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
