Pardon my ignorance if this is a stupid question, but I'm a network engineer, not an application programmer, and application packaging for distribution has me digging into this world deeper and deeper.

Installing .Net v2 does not take care of Apps needing 1.1? I installed Microsoft .net framework v2, thinking that would take care of all Apps needing .NET. Well my app wanted v 1.1 not 2.0, so I had to package v 1.1 as well. Seems illogical to me. I thought v 2 would take care of the need for prior versions.

Something here I am missing?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
That is my guessing too.
Install 1.1 + SP and then 2.0
Answered 02/01/2008 by: AngelD
Red Belt

Please log in to comment
0
*My* understanding is that .Net is backwards-compatible, i.e. 1.1 apps will be happy with 2.0. However, it could be that the 1.1 application's installer is testing for the presence of 1.1 and, not finding it, exits with an error to that effect. In that case, edit the installer (via a transform, if it's a vendor-supplied MSI) to either remove that test or change it to test for 2.0.

As ever, I'm happy to be corrected on my assumption on backward compatibility.
Answered 02/04/2008 by: VBScab
Red Belt

Please log in to comment
0
Sorry to disappoint, but it is indeed *NOT* backwards compatible. All versions, at least now, will happily coexist on a machine. If an app needs 1.1, you'll need that version. I just install them *ALL* as standard practice, to avoid problems in the future.

Hope that helps. [8|]
Answered 02/04/2008 by: mervync
Yellow Belt

Please log in to comment
0
This link may be of interest regarding the backward compatibility issues

http://msdn2.microsoft.com/en-us/library/ms994381.aspx


Regards,

Spartacus
Answered 02/04/2008 by: spartacus
Black Belt

Please log in to comment
0
ORIGINAL: spartacus

This link may be of interest regarding the backward compatibility issues

http://msdn2.microsoft.com/en-us/library/ms994381.aspx
My reading of the compatibility table suggests that I was right: a machine with 2.0 will load and run 1.1 apps. That opinion was gained when I was building installs for a software house who were just tipping their toe into .Net for their apps. However, the article also implies that processes can be set up to require 1.1 (or is it simply that they need to be recompiled with 2.0?) Mervyn?
Answered 02/05/2008 by: VBScab
Red Belt

Please log in to comment
0
From a real life scenario I've seen that 2.0 does not provide all functionallity from previous version(s) and therefore these versions was required to be installed for the (.NET) applications to work properly build on < 2.0..
Answered 02/05/2008 by: AngelD
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity