It seems like a fairly common task to check if a registry entry exists or not and then respond accordingly. In this situation, it would not be an error if the registry entry does not exist -- in fact in some cases it's expected.
The "failonerror" attribute to the readregistry task helps a bit here -- at least the build won't stop. There is still a warning though and in the case described here it seems unwarranted. I'd like to see an additional "reportwarning" type of attribute that could optionally be set to false (default would be true). In this case if a registry key doesn't exist, no warning would be reported. Example: <readregistry property="AppDir" failonerror="false" reportwarning="false" key="SOFTWARE\SomeKey" /> Regards, T.G. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
