Desktop Panel (Windows Embedded CE 6.0)

Article
01/05/2012

1/6/2010

The Desktop panel specifies desktop-side file configuration and plug-in object name. Each of the desktop-side files can be associated with a locale, in case your desktop-side code is localized for multiple locales, and each locale is a separate binary file.

The following table describes the elements of this panel.

Element	Description
Plug-in object name	Specifies the plug-in main object name, which is the name of the main Microsoft.RemoteToolSdk.PluginComponent implementation in your plug-in, preceded by the namespace (for example, MyPlugin.Plugin).
Files in desktop component	Lists desktop-side file components. A file component is an abstraction of a file over one or more locales. That is, file component A may refer to [C:]\myfolder\en-us\myplugin.dll for English, [C]:\myfolder\ja\myplugin.dll for Japanese, and so forth. To add a file component, click Add Component, and then click the newly added file component to rename it. To remove a file component, click the file component, click Remove, and then click Yes to confirm the deletion. The primary component is the .NET assembly with the Microsoft.RemoteToolSdk.PluginComponent implementation that the Remote Tools shell loads. To make a file component a primary component, select a file component in this box, and then select the Primary Component check box. Note: Only a single component can be designated as the primary component. To make a file component locale-independent, select Locale independent. Note that the paths in Paths in <Component name> are set to Any as the locale, which means that the file is used by all locales.
Paths in <Component name>	Lists desktop-side files in the selected file component. To edit the file path of a file in this list, double-click its path column in the Paths in <Component name> box. In the Open dialog box, you can select a file. If the file does not exist on your system at the time of editing, you can type the path in the box next to Generalize Path. To shorten file paths, you can use variable substitutions for the path name. Click Generalize Path to assign variables to specific directory levels.

Plug-in object name

Specifies the plug-in main object name, which is the name of the main Microsoft.RemoteToolSdk.PluginComponent implementation in your plug-in, preceded by the namespace (for example, MyPlugin.Plugin).

Files in desktop component

Lists desktop-side file components. A file component is an abstraction of a file over one or more locales. That is, file component A may refer to [C:]\myfolder\en-us\myplugin.dll for English, [C]:\myfolder\ja\myplugin.dll for Japanese, and so forth.

To add a file component, click Add Component, and then click the newly added file component to rename it.

To remove a file component, click the file component, click Remove, and then click Yes to confirm the deletion.

The primary component is the .NET assembly with the Microsoft.RemoteToolSdk.PluginComponent implementation that the Remote Tools shell loads. To make a file component a primary component, select a file component in this box, and then select the Primary Component check box.

Note:

Only a single component can be designated as the primary component.

To make a file component locale-independent, select Locale independent. Note that the paths in Paths in <Component name> are set to Any as the locale, which means that the file is used by all locales.

Paths in <Component name>

Lists desktop-side files in the selected file component.

To edit the file path of a file in this list, double-click its path column in the Paths in <Component name> box. In the Open dialog box, you can select a file. If the file does not exist on your system at the time of editing, you can type the path in the box next to Generalize Path.

To shorten file paths, you can use variable substitutions for the path name. Click Generalize Path to assign variables to specific directory levels.

Partager via

Desktop Panel (Windows Embedded CE 6.0)

See Also

Concepts

Ressources supplémentaires