How to Create a Manifest for an RTC Client Application
This topic describes how to create a manifest for your RTC client application.
To deploy applications that use the RTC Client API 1.3 on computers running Windows XP, you must create an application manifest and deploy it with your application. For more information about using side-by-side assemblies and side by side in general, see Using Side-by-Side Assemblies.
To create a manifest for your application
- Copy this sample manifest and paste it into any text editor.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> <assemblyIdentity version="18.104.22.168" processorArchitecture="x86" name="ISVName.ISVDivision.ISVapp" type="win32" /> <description>Your app description here</description> <dependency> <dependentAssembly> <assemblyIdentity type="win32" name=" Microsoft.Windows.Networking.RTCDLL" version=" 5.2.1002.3" processorArchitecture="X86" publicKeyToken="6595b64144ccf1df" language="*" /> </dependentAssembly> </dependency> </assembly>
- Edit the information in the manifest to make it appropriate for your application. To do this, change the featured value of the first <assemblyIdentity> element as follows:
- For the version attribute, set the value to the current version number for your component or application. This number is specified in the properties for your project when it is built using Microsoft® Visual Studio.
- For the processorArchitecture attribute, change the value of the processor architecture only if you are deploying to a processor architecture that is not Intel-x86 compatible. Otherwise, use the suggested default.
- For the name attribute, set the value to the registered name for your application. For most Windows applications, you only need to replace "mysampleapp" with the base name of the executable (.exe) file containing your application.
- For the type attribute, change the value only if you are deploying to a version of Windows that does not run under the Windows API. Otherwise, use the suggested default.
- Update the description for your application. The <description> element is optional, so you can either update its contents to include a brief description of your application or remove it from your manifest code. If you choose to remove it, be sure to remove both its opening and closing tags and any character data contained within them.
- For the dependent assembly section, update the featured attribute values for the <assemblyIdentity> element so that its values are appropriate to the version of RTC Client API 1.3.
Note The version attribute is 5.2.1002.3. For future releases, the version number will be different. This will mean changing the version number to the appropriate number when those binaries become available.
To identify the version number of the Rtcdll.dll, run Rtcapisetup.exe to install the RTC API. This will give the Dir %windir%\winsxs\*rtc* value for the current version.
The version is 5.1.1.0000 if the value is x86_Microsoft.Windows.Networking.RtcDll_6595b64144ccf1df_22.214.171.124_x-ww_91d50d8f.
The version is 5.2.1.0000 if the value is x86_Microsoft.Windows.Networking.RtcDll_6595b64144ccf1df_5.2.1.0000_x-ww_09834345.
- Save the application manifest to a file in the same directory as the executable file for your application. Name your manifest file so that it has the same name as your application, and add the ".manifest" extension to the end of it. For example, if your application executable is called Test.exe, the manifest file should be named Test.exe.manifest.
- Decide how to package and deploy your application manifest with your application.
As an alternative for new applications, you can include the application manifest directly in the resource (.rc) file for your application. In this case, also add the following line to the resource (.rc) file:
CREATEPROCESS_MANIFEST_RESOURCE_ID RT_MANIFEST "YourApp.exe.manifest"
Be sure to update "YourApp.exe.manifest" with the name for your manifest file. After you add the preceding line to your application header file, the manifest will be directly included with your application binary file the next time it is compiled. If you do not choose to include the manifest in this way, include the manifest file separately in the Windows Installer package (.msi) that you create to install your application.
Note If you provide your manifest both separately and internally in the resource section of your compiled executable, the file system version of your manifest will take precedence over the one included with the executable file in Windows XP and Windows XP SP1. However, the internal resource manifest will take precedence in Windows Server 2003.
- Test your application to ensure that you get the results you want. Testing your application before deployment is always important, but you should be sure that your test computer does not already have the side-by-side assembly for the RTC Client API 1.3 already registered on it. Otherwise, your testing will be compromised and the results will be incorrect.
- To deploy or update your application as a Windows Installer package, merge the Rtcclnt.msm merge module with your setup package.