home *** CD-ROM | disk | FTP | other *** search
- <assembly manifestVersion="1.0" description="" displayName="" company="MS" copyright="" supportInformation="" creationTimeStamp="2006-01-03T01:01:33.6028792-07:00" lastUpdateTimeStamp="2006-01-03T17:43:48.5230435-07:00" authors="anoopc" owners="anoopc" testers="nareshc" buildFilter="" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:schemas-microsoft-com:asm.v3">
- <assemblyIdentity publicKeyToken="$(Build.WindowsPublicKeyToken)" buildType="$(build.buildType)" buildFilter="" versionScope="nonSxS" name="Microsoft-Windows-Fax-Server-DL" version="0.0.0.0" processorArchitecture="*" language="*"></assemblyIdentity>
- <migration scope="Upgrade,MigWiz,USMT" xmlns="">
- <!-- Declare for which Longhorn equivalent OC this manifest corresponds too -->
- <registerSDF name="FaxServiceRole"></registerSDF>
- <registerSDF name="FaxServiceConfigRole"></registerSDF>
-
- <migXml>
- <!-- First Check if fxsclnt.exe is present in the downlevel. If not, then bail out.
- Generally people check for the presence of registry keys to see if an Optional Component is
- present in the downlevel. But I felt this is not the right approach for us, since we do
- not remove the registry keys cleanly when fax is uninstalled. But fxsclnt.exe is sure to be
- absent even in such cases. -->
- <detects>
- <detect>
- <condition>MigXmlHelper.DoesObjectExist("File", "%systemroot%\system32\[fxsclnt.exe]")</condition>
- </detect>
- </detects>
-
- </migXml>
- <migrationDisplayID>Communications_and_Sync\Fax</migrationDisplayID>
- </migration>
- </assembly>
-
-