KenW wrote:
On Tue, 3 Oct 2017 23:58:59 -0500, VanguardLH wrote:

T wrote:

Apparently, I have to have "exactly" dot net 3.5 to get Cobian Backup
to work with Volume Shadow Service (VSS).

Is there any trick to this, or just go somewhere on M$ web site
and download and install it?
https://docs.microsoft.com/en-us/dot...m-requirements

Nothing less than .NET Framework 4 (back on Windows XP) is listed as
installable. For Windows 10, the tables says nothing less than the
included 4.7 is installable in the Creators edition (which I have to
assume is what you have).

https://docs.microsoft.com/en-us/dot...d-dependencies

That's presents differing compatibities regarding what .NET version is
included or can be installed on what version of Windows. That says .Net
3.5 is already bundled in Windows 10. To find what versions of .Net
that are currently installed, see:

https://docs.microsoft.com/en-us/dot...-are-installed

To check about .Net 3.5 in your instance of Windows 10, go look under
the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP
registry key to see if a 3.5 subkey is listed under there. So are you
sure your Windows 10 does not already have .NET Framework 3.5 installed?

If it is missing from your particular Windows 10 install, you can grab a
download of the 3.5 installer at:

https://www.microsoft.com/en-us/down...ils.aspx?id=21
https://docs.microsoft.com/en-us/dot...-35-windows-10

As I recall, the installer will check if a version has dependencies with
prior versions; i.e., some versions won't install unless the requisite
prior version(s) is(are) installed. 3.5 is an incremental update from
3.0 so you need 3.0, too.

https://en.wikipedia.org/wiki/.NET_F...elease_history

That shows 3.5 was the last minor version within that major version.
There wasn't a later version that might modify or rely upon 3.5.

You sure you aren't being disingenuous to your paying customers who want
a real human instead of getting presented with a frankenstein?
Cobian Backup development died back in Dec 2012 - but you already knew
that. That's why you keep repairing Cobian Backup. If they are paying
you, "free" is not their only criteria for a backup solution.

You can install older versions. At least with Win 7, I was able to get
1.1 (I think) there was even instruction howto. Of course Win 10 is a
different animal, Soooooooooo !


KenW

There are hints here.

https://en.wikipedia.org/wiki/.NET_Framework

Rev. CLR Date

1.0 1.0 2002-02-13
1.1 1.1 2003-04-24

2.0 2.0 2005-11-07
3.0 2.0 2006-11-06
3.5 2.0 2007-11-19

4.0 4 2010-04-12
4.5 4 2012-08-15
4.5.1 4 2013-10-17
4.5.2 4 2014-05-05
4.6 4 2015-07-20
4.6.1 4 2015-11-30
4.6.2 4 2016-08-02
4.7 4 2017-04-05

*******

Programs that ask for CLR 1.1, won[t be satisfied by other versions.
Modern OSes won't be dependent on 1.1 either. That gives a degree
of freedom.

I don't think a program looking for CLR 2, would particularly
be pleased with CLR 4, but I cannot verify that from the available
documentation. Because the approach (big release, mini release
followed by big update, newer release replaces older release)
has changed over the years, and the web articles might still
not have enough detail to figure it out.

There would not be a tick box for 3.5 in Windows Features, unless
it was a compatibility solution for older code. That would be
my evidence that installing 4.x with CLR 4, doesn't solve
a CLR 2 requirement from an application.

Paul