net framework 2.0 if not present to popup a message
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"
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
Answers (13)
Please log in to answer
Posted by:
AngelD
13 years ago
Is the launch condition action sequenced after appsearch (system search)?
Posted by:
honeyslim
13 years ago
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.
It’s not working.
Posted by:
anonymous_9363
13 years ago
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'.
Posted by:
honeyslim
13 years ago
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 .
'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\IEHost.dll'.
where i have to mention like in condition or Value name .
Posted by:
anonymous_9363
13 years ago
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.
To be kind, I was suggesting that you change the search from a registry search to a file search.
Posted by:
honeyslim
13 years ago
Changed the registry search to a file search. Still not working same error :(
Posted by:
anonymous_9363
13 years ago
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.
- 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.
Posted by:
timmsie
13 years ago
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
Wise then adds it's own custom action WiseGetDotNetVersion and Launch Condition
Posted by:
cygan
13 years ago
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
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
Posted by:
honeyslim
13 years ago
HiPackagers
Done all above thinks still same error. plz share your other ideas .
Done all above thinks still same error. plz share your other ideas .
Posted by:
anonymous_9363
13 years ago
Have you stepped through the package using the WPS debugger? It will show you the sequence of actions and the value of properties etc.
Posted by:
honeyslim
13 years ago
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.
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.
Posted by:
anonymous_9363
13 years ago
I can't even remember ever using v5.1 so I couldn't say. I don't see why it wouldn't, though.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.