Pitney Bowes MapXtreme - Manual (Page 612)

Appendix K: Localization Kit
How to Use the Localization Kit
MapXtreme v7.1 619 Developer Guide
LocalizationKit.proj
The LocalizationKit.proj targets are:
build - builds the LocalizationKit solution and calls the LocalizationKit.Utilities project's
"RegisterSkipVerifiection" target (default target)
rebuild - rebuilds the LocalizationKit solution and calls the LocalizationKit.Utilities project's
"RegisterSkipVerification" target
clean - deletes all the output satellite assemblies and any intermediate files as a part of the build
process
LocalizationKit.Utilities.proj
The LocalizationKit.Utilities.proj targets are:
RegisterSkipVerification - Registers all the satellite assemblies to skip verification by running the
sn.exe -Vr <assembly_name> command (default target)
UnregisterSkipVerification - Unregisters all the satellite assemblies to skip verification by running the
sn.exe -Vu <assembly_name> command
InstallGac - Installs the satellite assemblies into the Global Assembly Cache by running the
gacutil.exe /I <assembly_name> /f command
UninstallGac -Uninstalls the satellite assemblies from the Global Assembly Cache by running the
gacutil.exe /uf <assembly_name> command
Acceptable values for the project’s configuration property are debug (default) and release. See
below for usage.
The LocalizationKit project file depends upon and uses the targets in the LocalizationKit.Utilities
project file.
L
For developers using Visual C# 2008 Express Edition, you will have to add MSBuild and the
directory containing the Strong Name Utility and Global Assembly Cache Utility to your
system path.
Given these path locations,
MSBuild (msbuild.exe) - C:\WINDOWS\Microsoft.NET\Framework\v3.5
Strong Name Utility (sn.exe) and Global Assembly Cache Utility (gacutil.exe) - C:\Program
Files\Microsoft SDKs\Windows\v6.0A\bin
,the line in the command prompt would be,
LocalizationKit> set
path=%path%;C:\WINDOWS\Microsoft.NET\Framework\v3.5;C:\Program
Files\Microsoft SDKs\Windows\v6.0A\bin
The directory paths on your machine may be very different, so be sure to use the correct paths in
your environment.
To build the Localization Kit, run this command from the kit's root directory: