|
.NET DotNet Forum Index » Visual C# Forum » Why is it.......
Page 1 of 1
|
| Author |
Message |
| JDeats... |
 Posted: Thu Sep 04, 2008 2:32 pm |
|
|
|
Guest
|
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. |
|
|
| Back to top |
|
| JDeats... |
| Posted: Thu Sep 04, 2008 2:34 pm |
|
|
|
Guest
|
Before someone pipes in with The .NET Framework isn't available on Mac
OS.... I was making an abstract generalization. |
|
|
| Back to top |
|
| JDeats... |
| Posted: Thu Sep 04, 2008 4:24 pm |
|
|
|
Guest
|
On Sep 4, 8:42 pm, Arne Vajhøj <a... at (no spam) vajhoej.dk> wrote:
Quote: JDeats wrote:
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
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. |
|
|
| Back to top |
|
| Arne Vajhøj... |
| Posted: Thu Sep 04, 2008 8:42 pm |
|
|
|
Guest
|
JDeats wrote:
Quote: 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 |
|
|
| Back to top |
|
| Peter Duniho... |
| Posted: Thu Sep 04, 2008 9:41 pm |
|
|
|
Guest
|
On Thu, 04 Sep 2008 19:24:33 -0700, JDeats <Jeremy.Deats at (no spam) gmail.com> wrote:
Quote: 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.
Yes, it could help. But, if it takes an OS patch to do it, why bother?
Just have the user install .NET. And are you going to patch every version
of Windows that ever existed? Implementations that wouldn't require a
patch could wind up fairly complicated, depending on just how far back you
want to support for error messages.
By the way, the Mac OS certainly has its own foibles of a similar nature.
Try running an OS X application on OS 9, for example.
In the end, users need to take some responsibility for being aware of
system requirements for programs they want to run. There's only so much
that could be done in terms of providing more specific error messages
while still avoiding issues like bloating applications and wasting
development time implementing this sort of thing.
Pete |
|
|
| Back to top |
|
| Arne Vajhøj... |
| Posted: Thu Sep 04, 2008 9:49 pm |
|
|
|
Guest
|
JDeats wrote:
Quote: On Sep 4, 8:42 pm, Arne Vajhøj <a... at (no spam) vajhoej.dk> wrote:
JDeats wrote:
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 !
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 |
|
|
| Back to top |
|
| |
