2.6.2. File Locations


2.6.2. File Locations
Prev	2.6. Managing Files	Next

The various WebView files have different locations, depending on their source and purpose. There are two general locations: for installed content, and for user content; and within user content you'll find your organization content.

Installed Content - `[WebRoot]`

Installed content is read-only, not to be modified by the user. It is installed (and re-installed) whenever the DataHub program is installed, and includes the stock WebView demo pages. Installed content is located here (32-bit/64-bit versions of the DataHub program):

C:\Program Files (x86)\Cogent\Cogent DataHub\plugin\WebServer\html\Content\
C:\Program Files\Cogent\Cogent DataHub\plugin\WebServer\html\Content\

We use the placeholder [WebRoot] in this document to refer to this path.


	This path, up to `html` is the default DataHub install directory. It is also the document root directory for the DataHub Web Server, and can be reconfigured in the Properties window Web Server option, if desired.

User Content - [UserContentRoot]
User content such as pages, images, scripts, and so on is read/write, and is located in this directory:
```
C:\Users\<username>\AppData\Roaming\Cogent DataHub\WebContent\Content\
```
We use the placeholder [UserContentRoot] in this document to refer to this path.
You can change this path using the -H DataHub command-line option, or by setting it through the DataHub Service Manager application.

Your Organization Content - `[OrgLocal]`

The path for files pertaining to your organization is:

[UserContentRoot]\Organizations\Local\

We use the placeholder [OrgLocal] in this document to refer to this path. Within it are sub-directories for various types of files. Here are some examples of types of users and the directories for the files they would typically use:

Type of Users	Typically use files in these sub-directories
Operators	[OrgLocal]\Pages
Page builders	[OrgLocal]\Pages [OrgLocal]\Images [OrgLocal]\Media
Advanced/Admin	[OrgLocal]\Branding [OrgLocal]\Scripts
Control Developers	[OrgLocal]\Controls [OrgLocal]\ControlAssemblies [OrgLocal]\Symbols

There are two possible instances of each of these directories: for shared content, and for user-specific content, and each can optionally have sub-directories.

Shared Content
This content is available to all logged-in WebView users in your organization. For example:
```
[OrgLocal]\Pages\TestPage1.xml
[OrgLocal]\Pages\<optional sub-directory>\TestPage1.xml
```
User-Specific Content
User-specific content is available only to users logged into the WebView application with a given user name. This content is placed in the Users sub-directory, and organized in a parallel way to shared content. For example:
```
[OrgLocal]\Users\<username>\Pages\MyPage1.xml
[OrgLocal]\Users\<username>\Pages\
                   <optional sub-directory>\MyPage1.xml
```

And finally, there is one more aspect of user content organization that is relevant only to developers of custom controls.

Custom Controls
Starting with DataHub Version 9, custom controls and control assemblies were differentiated between Silverlight and WPF (used by Desktop WebView) versions. Now Microsoft has deprecated Silverlight, and Desktop WebView is referred to as simply WebView.
Legacy WebView controls created in Silverlight will only work in Silverlight. Those created in WPF will only work in the Desktop WebView application. You need to compile these controls separately for the Desktop or Silverlight WebView applications. For example:
```
[OrgLocal]\Controls\<publisher>\
[OrgLocal]\Controls\<publisher>\Silverlight\
[OrgLocal]\Controls\<publisher>\WPF\

[OrgLocal]\ControlAssemblies\Silverlight\<publisher>\
[OrgLocal]\ControlAssemblies\WPF\<publisher>\
```
You must similarly distinguish XAML and XML files for your custom controls if they are different between Silverlight and WPF versions.


	You can change this path using the `-H` DataHub command-line option, or by setting it through the DataHub Service Manager application.