Charles,
You can check the Registry and populate a variable in your MSI package with
the version of the Framework that is installed. You would need to use a
custom action to do it or a tool such as Wise for Windows Installer or
InstallShield to do it easily.
As for the crash you are having, here is a list of breaking changes in 1.1:
http://www.gotdotnet.com/team/change...ault.aspx#0000
0173
Jim Cheshire [MSFT]
Developer Support
ASP.NET
(E-Mail Removed)
This post is provided as-is with no warranties and confers no rights.
--------------------
>From: "charles" <(E-Mail Removed)>
>Subject: ASP.Net Versions and Compatibility
>Date: Thu, 30 Oct 2003 12:47:19 -0800
>Lines: 12
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
>Message-ID: <O73E$(E-Mail Removed)>
>Newsgroups: microsoft.public.dotnet.framework.aspnet
>NNTP-Posting-Host: cust-ip-216-222-97-9.boi.rmci.net 216.222.97.9
>Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
>Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.aspnet:187648
>X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
>
>I ship a C# asp.net app in .dll form which is targeted at ASP.Net v1.1.
>
>If a user loads is on a machine with ASP.Net v1.0, it crashes--no
reasonable
>message--just a null-pointer exception before any of my code is reached..
>
>Is there a standard practice to detect and/or prevent this situation. I
>haven't found an option in the installer to detect the asp.net version.
>
>thanks
>charles
>
>
>