M
Matt
I was wondering what the exact error message is when a user attempts to
run a .NET 2.0 application on a machine that does not have the
framework installed. I remember in 1.1 it was a nasty cryptic message
that was not at all helpful, has it improved any?
We are working on a simple tool that will run from a CD or whatever and
has a requirement that it is XCOPY, we cannot install it, is the
missing 2.0 error message human readable? Do we need to develop some
sort of native loader application to catch the missing CLR exception
and display something more user friendly?
Thanks!
run a .NET 2.0 application on a machine that does not have the
framework installed. I remember in 1.1 it was a nasty cryptic message
that was not at all helpful, has it improved any?
We are working on a simple tool that will run from a CD or whatever and
has a requirement that it is XCOPY, we cannot install it, is the
missing 2.0 error message human readable? Do we need to develop some
sort of native loader application to catch the missing CLR exception
and display something more user friendly?
Thanks!