Windows 10 Update 1607 seems to be removing .Net 3.5
-
This is the second time I have had a machine update to Windows 10 r1607 and then not have .Net 3.5
-
Snicker But new .net versions are supposed to be compatible with all the older ones!
Microsoft jokes, I tell ya.
-
@travisdh1 said in Windows 10 Update 1607 seems to be removing .Net 3.5:
Snicker But new .net versions are supposed to be compatible with all the older ones!
Microsoft jokes, I tell ya.
The problem is developers have to code applications against a .net version from what I can tell.
-
@JaredBusch said in Windows 10 Update 1607 seems to be removing .Net 3.5:
@travisdh1 said in Windows 10 Update 1607 seems to be removing .Net 3.5:
Snicker But new .net versions are supposed to be compatible with all the older ones!
Microsoft jokes, I tell ya.
The problem is developers have to code applications against a .net version from what I can tell.
In all actuality, it's much more likely programmers writing bad code than something Microsoft has done. The joys of Quickbooks needing very specific versions of .net libraries is ever so much fun to deal with.
-
@travisdh1 said in Windows 10 Update 1607 seems to be removing .Net 3.5:
@JaredBusch said in Windows 10 Update 1607 seems to be removing .Net 3.5:
@travisdh1 said in Windows 10 Update 1607 seems to be removing .Net 3.5:
Snicker But new .net versions are supposed to be compatible with all the older ones!
Microsoft jokes, I tell ya.
The problem is developers have to code applications against a .net version from what I can tell.
In all actuality, it's much more likely programmers writing bad code than something Microsoft has done. The joys of Quickbooks needing very specific versions of .net libraries is ever so much fun to deal with.
No, this is what I am talking about. When you develop an application in .Net, you have to select a target version.
So unless the developers recompile their code for the newer version of .Net, as I have done here, it will require the older version.
This was originally a .Net 2.0 application written by a predecessor a decade or more ago.
I rebuilt it (and everything else at this client) to compile against .net 4.5 back when they rolled to Windows 8.
-
@JaredBusch So how the [self-moderated] do certain, previously named, companies make things that require very specific not-quite-upgraded versions of certain components of .net? I mean, they target specific versions of files that are a part of .net. When I go bald, at least I'll know why!
-
@travisdh1 said in Windows 10 Update 1607 seems to be removing .Net 3.5:
@JaredBusch So how the [self-moderated] do certain, previously named, companies make things that require very specific not-quite-upgraded versions of certain components of .net? I mean, they target specific versions of files that are a part of .net. When I go bald, at least I'll know why!
Because they do not want to spend the money to recompile for newer versions in order to maintain a stupid high level of compatibility with people using old shit.
-
@JaredBusch said in Windows 10 Update 1607 seems to be removing .Net 3.5:
@travisdh1 said in Windows 10 Update 1607 seems to be removing .Net 3.5:
@JaredBusch So how the [self-moderated] do certain, previously named, companies make things that require very specific not-quite-upgraded versions of certain components of .net? I mean, they target specific versions of files that are a part of .net. When I go bald, at least I'll know why!
Because they do not want to spend the money to recompile for newer versions in order to maintain a stupid high level of compatibility with people using old shit.
You think they're actually bothering to use the tool you posted? Nope. They're checking the filenames on the system. I forget exactly which files they do this for, but it's super annoying because it didn't match with the latest updates or original version last time I had to install the P.O.S.
