Why is it....


J

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.
 
Ad

Advertisements

J

JDeats

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

Arne Vajhøj

JDeats said:
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
 
J

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.
 
A

Arne Vajhøj

JDeats said:
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
 
Ad

Advertisements

P

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
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top