|
|
|
Like it 
|
|
|
|
|
|
No idea. My code is perfect. 
Social Media - A platform that makes it easier for the crazies to find each other.
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
|
|
|
|
|
I can easily imagine answers to all three.
Why upgrading MS-SSMS have to upgrade ODBC drivers? It might depend on some extension available only in the new ODBC driver version. Or possibly the new version do not have new fuctions, but essential performance improvements. Or essential bugfixes.
And why an admittedly compatible update can not be done without total remove of the previous version? The currently installed version might be one of umpteen different ones, with all sorts of incompatibilities and other issues. Keeping a full catalog of all previous versions (in all regional variants, for all sorts of architectures, ...) telling which older modules can be kept and which must be replaced could be extremely difficult to maintain, and could make the install/upgrade procedures magnitudes more complex. Chances are that it wouldn't be much faster, either - simply showeling in the new version without asking any questions may be the fastest alternative, and certainly safest one. The installation package would have to include all modules anyway, just in case they were needed.
And why the update rely on a previous (maybe totally foobar) install? That could be for licensing reasons: An installed, older version proves that the user has provided a license for that install, so he doesn't need to present it again. (I've seen a few systems that were like that.) The installer might pick up license info from the old installation to incorporate into the new.
...Are you sure that you know what you really want? You seem to dislike that the update relies on a previous install, yet you seem to want it not to be removed (is that even if it is "totally foobar"?)
I know: Some software (often in huge program systems) do allow piecewise updates, leaving other, old modules untouched. This ususally requires a very strong programming discipline, where any change of module interfaces is a major architectural update. Some such systems also rely on every module being able to answer to requests from e.g. the installer about their version number, configuration etc. So it is possible, but it might require a lot of resources to maintain. For simpler systems, it may not be worth the effort. Besides, full replacement allows agile interface definitions, the way modern programmers expect them to be: Something that is defined by implementation, not by specification.
|
|
|
|
|
Don't ruin a perfectly good Microsoft hate session with your silly logic. 
Social Media - A platform that makes it easier for the crazies to find each other.
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
|
|
|
|
|
Because it's faster?
Fail early and fail often.
|
|
|
|
|
|
|
Turning on my setup this morning (basically microtower, display, sound thing)
nice little bang and flipped the sub and main home circuit breakers.
Anyway, I already guessed it was the semi-cheap sound system, but carefully checked the more valuable bits first - no probs.
Yup, 'twas the sound thing, or more accurately the power adapter (even before opening it I knew)
Ppened up the adapter - tiny shrapnel, slight board burn near a very telling gap between 2 severed at board level legs where a diode [I think] used to live.
Ordered a new adapter, better quality $25 (one with genuine medical grade safety cert #)
- yeah almost as much as whole a new unit, and yeah: could've had a new cheapo adapter for $9,
but I feel safer with the better quality adapter than with another fire hazard.
(and if the unit itself is toast who cares, I'll buy another same, and use my new adapter - the one I got fits no nicely almost completely out of sight in a small space behind the monitor.)
It's usually them adapters that worry me most, cheap, crap, (probably 1$ or less bulk OEM)
- but they're also the bit that closest to the 240V hurty hot pixies so not to be ignored.
pestilence [ pes-tl-uh ns ] noun
1. a deadly or virulent epidemic disease. especially bubonic plague.
2. something that is considered harmful, destructive, or evil.
Synonyms: pest, plague, CCP
|
|
|
|
|
Done that many times myself, the question is did the one you bought have a genuie Medical Cert? worth checking. I found with some I ordered at work the number was not genuie but was used as a way to complain and use the dread 'Fake Components' term in an email, which resulted in the entire batch being 'free', just check! 
|
|
|
|
|
When I began reading I was thinking, "Oh no...hope didn't lose entire rig".
Glad to hear that the damage was minimal and easily fixable.
|
|
|
|
|
Don't you know to not let the magic smoke out.
|
|
|
|
|
So, I've been working on this app that will generate model and viewmodel classes from stored procs in the specified database. It's intended for folks like me, that abhor the thought of using a UDM, or that find the ADO.Net project in Visual Studio to the quagmire of failure that it is.
Every time I think I've reached a point where I think I'm finally done, I think of something else that really must be included in the app.
0) It would be nice if I could do the same thing with tables and views. Result : a new wizard page, a new window, and a crapload of refactoring in the code generator. Thought I was finally done...
1) I decided to try out the long-ignored stored proc generator. Result: new window to handle procs with input parameters, and fixing some generator code. Thought I was finally done...
2) I decided I wanted to add more flexibility where the viewmodel generation was concerned. Result: Completely refactoring the settings wizard page, adding a help window for viewmodel settings, and adding code to react to the new settings. Thought I was finally done...
3) Item #3 is boycotted today. This item will not appear in any of my enumerated lists for the remainder of the day.
4) It might be nice to add properties that provide CRUD queries for tables. Result : adding code to the code generator that does creates the queries, and adding a number of new app settings to allow some flexibility. Thought I was finally done...
5) In the process of adding the CRUD stuff, a dilemma arose regarding how to identify the column that would control update and delete functionality. Originally, I looked for a column with the text "ID" in it. I sat there looking at the code, and thought, "Not everybody is as pragmatic as I am in their column naming habits, so I, after a little research, I discovered that the ADO DataColumn object contained properties to help you find columns that auto-increment and that are read-only. So, I changed the code to retain and look for those properties to identify the most likely ID column. The whole detection code block turned into a three-tier setup, where I look for the autoincrement/readonly column, fall back to one that looks for "ID" in the name, and then finally, simply use the first column in the returned schema.
Unless you count testing, testing, and more testing, and then writing the actual article series, I think I'm finally done...
Famous last words, right?
".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
modified 4-May-20 10:08am.
|
|
|
|
|
Maybe a nice idea to make it a cross-platform app 
|
|
|
|
|
It's got a WPF UI, so there's no hope of that happening. 
".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
|
|
|
|
|
I thought that what .Net Core is for...
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
.Net core is for commandline apps. If your app has a UI (WinForms or WPF), running in different versions of Windows is about as "cross-platform" as it gets.
They can't make a WPF layer because linux has a crap-ton of different compositors and graphics engines. Microsoft can't just pick one to support/endorse, but at the same time, they can't possibly support them all, so they chose the lazy path and decided not to do anything.
".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
|
|
|
|
|
This is like Docker on Windows: Consider it CLI only.
Well, a container might have an HTML interface, but that is not exactly like WPF.
In principle, I guess you in principle could create a container where UI libraries were replaced by stubs code running the Windows Remote Desktop protocol. The container would probably approach Windows itself in size. (Don't consider it a serious proposal  )
Linux people would say: Why don't you just do it our way - you could be using X11, then everything would be fine! ... Try telling Linux affecionados that they could simply implement the Windos way in Linux, abandoning X11, and listen to the reaction you get
|
|
|
|
|
Using docker containers is a) more work than it's worth, and b) running in a docker container STILL won't let the app run in Linux.
Using .Net Core would add NOTHING tangibly positive to a WPF or WinForms app. Since it's not a web app, I'm not even sure why you mentioned it.
".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
|
|
|
|
|
You can run WPF (or WinForms, or UWP) on .net core; but since it's just a wrapper for a bunch of Win32 UI libraries your application will only work on Windows because other platforms don't support the lower level dependencies.
Or won't until someone gets bored enough to package the libraries for WINE up nicely into a format that .net core can natively use anyway.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
WPF has been around since about 2009, and WINE *still* doesn't support it, as is evidenced by Wine's inability to run Visual Studio 2010 and newer (when they change the UI over to WPF).
Until Microsoft gets off their ass and provides the necessary graphics layers for use on Linux (which also won't ever happen), .Net Core is only "cross-platform" for CLI apps.
".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
|
|
|
|
|
#realJSOP wrote: Every time I think I've reached a point where I think I'm finally done,
 I pinched one of these from a guy in the 90s, I only stopped fiddling with it when I retired 20 years later. I still ran it from the debug build.
Never underestimate the power of human stupidity -
RAH
I'm old. I know stuff - JSOP
|
|
|
|
|
#realJSOP wrote: I think I'm finally done...
Ha! John, you've been at this long enough to know that software is never done.
"Go forth into the source" - Neal Morse
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
