Detecting .NET Framework 2.0 runtime env.

[Ron M. Newman]

Hi,

You install a .NET 2.0 winforms application on a machine that doesn't have
the 2.0 redistributable s and then run it. How do you elegantly detect that
and warn your users? Any way to avoid ugly uncontrollable error boxes?

Thanks
Ron

[Chris Dunaway]

Ron M. Newman wrote:

You install a .NET 2.0 winforms application on a machine that doesn't have
the 2.0 redistributable s and then run it. How do you elegantly detect that
and warn your users? Any way to avoid ugly uncontrollable error boxes?

That's kind of a vicious circle! If the .Net Framework 2.0 is not
installed, your program will not run anyway, so it cannot detect if the
framework is there. You might be able to create some sort of launcher
app in C++ native code that can check for the framework and if present,
it launches the app.

[Ron M. Newman]

Yeah, i thought about it. So assuming I am creating a typical Win32 app
that'll launch the .NET executable, what do I look for in order to make sure
the .NET 2.0 is properly installed? any magical registry element I can refer
to? a file somewhere? what would be the most reliale check?

Ron

"Chris Dunaway" <du******@gmail .comwrote in message
news:11******** ************@i1 2g2000cwa.googl egroups.com...

Ron M. Newman wrote:

>You install a .NET 2.0 winforms application on a machine that doesn't
have
the 2.0 redistributable s and then run it. How do you elegantly detect
that
and warn your users? Any way to avoid ugly uncontrollable error boxes?

That's kind of a vicious circle! If the .Net Framework 2.0 is not
installed, your program will not run anyway, so it cannot detect if the
framework is there. You might be able to create some sort of launcher
app in C++ native code that can check for the framework and if present,
it launches the app.

[Michael Nemtsev]

Hello Ron,

Read there http://laflour.spaces. live.com/blog/cns!7575E2FFC19 135B4!393.entry

RNYeah, i thought about it. So assuming I am creating a typical Win32
RNapp that'll launch the .NET executable, what do I look for in order
RNto make sure the .NET 2.0 is properly installed? any magical
RNregistry element I can refer to? a file somewhere? what would be the
RNmost reliale check?
RN>
RNRon
RN>
RN"Chris Dunaway" <du******@gmail .comwrote in message
RNnews:11****** **************@ i12g2000cwa.goo glegroups.com.. .
RN>

>Ron M. Newman wrote:

>>You install a .NET 2.0 winforms application on a machine that
doesn't
have
the 2.0 redistributable s and then run it. How do you elegantly
detect
that
and warn your users? Any way to avoid ugly uncontrollable error
boxes?

That's kind of a vicious circle! If the .Net Framework 2.0 is not
installed, your program will not run anyway, so it cannot detect if
the framework is there. You might be able to create some sort of
launcher app in C++ native code that can check for the framework and
if present, it launches the app.

---
WBR,
Michael Nemtseva [C# MVP] :: blog: http://spaces.live.com/laflour

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

[Oliver Sturm]

Hello Ron,

>You install a .NET 2.0 winforms application on a machine that doesn't have
the 2.0 redistributable s and then run it. How do you elegantly detect that
and warn your users? Any way to avoid ugly uncontrollable error boxes?

Your installer should notice that a requirement for your application is
not fulfilled on the system and either refuse to install the application
or install the .NET Framework 2 before installing the application.
Oliver Sturm
--
http://www.sturmnet.org/blog