My purpose is to check net framework 2.0 if not present to popup a message
For that below condition given but it’s not working, could help any one it’s great for me .
DOTNET2 in the properties section to Null
In System Search - Property - DOTNET2
Operation - Read raw value from registry
Root - HKEY_LOCAL_MACHINE
Key -SOFTWARE\Microsoft\.NETFramework\policy\v2.0
Value Name – 50727
Launch condition - DOTNET2="50727-50727"
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Is the launch condition action sequenced after appsearch (system search)?
Answered 12/02/2010 by: AngelD
Red Belt

Please log in to comment
0
Yes it’s taken action the MSI I trying to install in .net 2.0 machine it’s giving a popup” You must have .NET framework 2.0 to install this package “ as per the my condition it’s should work in .net 2.0 machine
It’s not working.
Answered 12/03/2010 by: honeyslim
Senior Yellow Belt

Please log in to comment
0
Although Microsoft document registry interrogation to be the way to detect .Net Framework versions (although not the value you're getting), I prefer to detect the presence of a core file. This varies from version to version (naturally...) but, for v2, I use 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\IEHost.dll'.
Answered 12/03/2010 by: VBScab
Red Belt

Please log in to comment
0
I am getting confuse here
'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\IEHost.dll'.
where i have to mention like in condition or Value name .
Answered 12/03/2010 by: honeyslim
Senior Yellow Belt

Please log in to comment
0
To be brutally honest, if you don't understand my response, you really shouldn't be anywhere near MSIs.

To be kind, I was suggesting that you change the search from a registry search to a file search.
Answered 12/03/2010 by: VBScab
Red Belt

Please log in to comment
0
Changed the registry search to a file search. Still not working same error :(
Answered 12/03/2010 by: honeyslim
Senior Yellow Belt

Please log in to comment
0
I'm going to guess here...

- You have Wise Package Studio
- As Kim suggested, you haven't altered the default relationship, sequence-wise, between the AppSearch and LaunchCondition actions.

Clearly, if LC occurs before AS, then whatever AS finds cannot be processed by LC, since LC has already executed.
Answered 12/03/2010 by: VBScab
Red Belt

Please log in to comment
0
if you do have wise package studio then all you need to do in "Installation Expert" under "System Requirements" is change the .NET Framework Version to Version 2.0.50727

Wise then adds it's own custom action WiseGetDotNetVersion and Launch Condition
Answered 12/03/2010 by: timmsie
Fourth Degree Brown Belt

Please log in to comment
0
lets get back to basics.

have a look at the free demo videos on appdeploy on how to do an appsearch.


you can also do a search for appsearch and you will get lots of info
Answered 12/04/2010 by: cygan
Fifth Degree Brown Belt

Please log in to comment
0
HiPackagers
Done all above thinks still same error. plz share your other ideas .
Answered 12/08/2010 by: honeyslim
Senior Yellow Belt

Please log in to comment
0
Have you stepped through the package using the WPS debugger? It will show you the sequence of actions and the value of properties etc.
Answered 12/08/2010 by: VBScab
Red Belt

Please log in to comment
0
Hi all
thanks for your support :) it's working fine in Wise package 7.0 version but still i am facing the same problem in wise package 5.1 could you please let me know above condition will work in 5.1 version or not.
Answered 12/09/2010 by: honeyslim
Senior Yellow Belt

Please log in to comment
0
I can't even remember ever using v5.1 so I couldn't say. I don't see why it wouldn't, though.
Answered 12/09/2010 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity