"Matt" <matt.ski***@gmail.com> wrote in message
news:1161738105.073379.106300@h48g2000cwc.googlegroups.com...
>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!
>

> "Matt" <matt.ski***@gmail.com> wrote in message
> news:1161738105.073379.106300@h48g2000cwc.googlegroups.com...
> >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!
> >
>
>
> I would defintely write a small app that runs first.  It would look for the
> dot net registry keys and if they don't exist tell the user.
>
> I seem to remember testing this a while back and the error was one of those
> generic "A DLL required for this application could not be found" type of
> messages.