"Wencheng Magiya" <2ioh7zf02@sneakemail.com> wrote in message
news:eyXg3HTqFHA.3768@TK2MSFTNGP10.phx.gbl...
> Hi,
>
> Anybody know how to modify the setup project's .NET Framework Launch
> Condition to detect Framework 1.1 SP1 instead of 1.1?
>
> Cheers!
> Wencheng
>

"Phil Wilson" <Phil.Wilson@unisys.spamcom> wrote in message
news:%23Y63USoqFHA.4072@TK2MSFTNGP09.phx.gbl...
> This works but it's a lousy solution because it's a string comparison.
> However it's just about the only option that lets you use the VS IDE to
> set it. MsiNetAssemblySupport is the case-sensitive name of a Windows
> Installer property that's a string-valued version. So if you add a new
> condition
>
> MsiNetAssemblySupport > "1.1.4322.2299"
>
> where SP1 is 2300 in the patch IIRC.
>
> Another method which again is very 1.1 specific is to add a File Search to
> Search Target Machine. Search for fusion.dll in
> [WindowsFolder]Microsoft.Net\Framework\v1.1.4322 and use a MinVersion
> property of 1.1.4322.2299. Have a Property name such as GOODFUSION. Then
> add a launch condition and put GOODFUSION in the Condition.
> --
> Phil Wilson [MVP Windows Installer]
> ----
> "Wencheng Magiya" <2ioh7zf02@sneakemail.com> wrote in message
> news:eyXg3HTqFHA.3768@TK2MSFTNGP10.phx.gbl...
>> Hi,
>>
>> Anybody know how to modify the setup project's .NET Framework Launch
>> Condition to detect Framework 1.1 SP1 instead of 1.1?
>>
>> Cheers!
>> Wencheng
>>
>
>