Why is it....

[JDeats]

Here's just something I was wondering about in general that's bothered
me for many years.

Why is it that when you double click on an .NET Framework .exe on a
system that does not have the .NET Framework installed a Windows
exception error dialog appears?

Why couldn't Microsoft just put a bit of code in the managed .EXE to
detect if the required Framework is installed and if not prompt the
user with a meaningful dialog such as "This application requires
the .NET Framework 2.0 in order to run? Would you like to download and
install the .NET Framework 2.0 now"?

Having spent a bit of time behind Mac OS X, it's little details like
this that separate the two operating systems. I'm not saying Mac OS X
is perfect, but there are several details that make the OS cater to
end users in little ways that I think could be implemented by
Microsoft engineers, but haven't been priorities for whatever reason.

 

[JDeats]

Before someone pipes in with The .NET Framework isn't available on Mac
OS.... I was making an abstract generalization.

 

[Arne Vajhøj]

Here's just something I was wondering about in general that's bothered
me for many years.

Why is it that when you double click on an .NET Framework .exe on a
system that does not have the .NET Framework installed a Windows
exception error dialog appears?

Why couldn't Microsoft just put a bit of code in the managed .EXE to
detect if the required Framework is installed and if not prompt the
user with a meaningful dialog such as "This application requires
the .NET Framework 2.0 in order to run? Would you like to download and
install the .NET Framework 2.0 now"?

That would require native code in every .NET EXE !

Arne

 

[JDeats]

That would require native code in every .NET EXE !

Arne

It would be accomplished through an OS patch.... We could go round and
round about why this approach is proper or not, the point is it would
benefit the end users who might happen to find themselves with
an .NET .exe they can't run an generic Windows exception message.

 

[Arne Vajhøj]

It would be accomplished through an OS patch....

Install something that know enough about .NET assemblies to
recognize them but not enough to run them ?

I guess you could.

Arne

 

[Marc Gravell]

Install something that know enough about .NET assemblies to

recognize them but not enough to run them ?

I guess you could.

So assuming you want something small(ish), the Client Profile would be
a better option:

http://msdn.microsoft.com/en-us/library/cc656912.aspx

28MB instead of 230-ish MB might make things easier to deploy...

Of course, full .NET would be preferable ;-p

Marc

 

[Peter Morris]

I agree. In my experience it hasn't even shown a windows error box.
However, I think that bringing OSX into the statement has no relevance to
your statement



Pete