Webdav

From Sense/Net Wiki
Jump to: navigation, search
  •  
  •  
  •  
  •  
  • 100%
  • 6.0.1
  • Enterprise
  • Community
  • Planned

sensenet 7: this article has a more recent version on the new community site.

Overview

Sense/Net provides a way to access your content via webdav, allowing Microsoft Office, Windows Explorer, Total Commander, Visual Studio, etc to open and edit content residing in a Sense/Net Content Repository. The Content Repository can be even mapped as a drive. Office documents can be opened directly from the portal surface with webdav. When a document opened via webdav is saved, it is automatically versioned, permissions are automatically checked, etc. Drag and drop move and copy also works.

Details

Installation

Webdav automatically works in Sense/Net, but there are a few things you may have to configure before you can access your Content Repository as a file system.

Authentication

Sense/Net supports the following authentication schemes with webdav:

  • Windows authentication
Set up both your Sense/Net Site to use Windows authentication, and your IIS web site to allow Windows authentication. Make sure your AD user is present in the Content Repository under the appropriate domain. You will be able to access the Content Repository using your AD user and password.
  • Basic authentication
Set up your Sense/Net Site to use Forms authentication, and your IIS web site to allow Anonymous authentication only (do not allow Windows in IIS and allowing Basic is not necessary). You will be able to access the Content Repository using your portal user and password. Please note that operations that use Basic authentication over a non-SSL HTTP connection are disabled by default by your operating system. To enable webdav for non-SSL sites with Basic authentication refer to the following article: http://support.microsoft.com/kb/2123563.

Please note that support for Basic authentication has been introduced in Sense/Net 6.1. Any versions prior must use Windows authentication for using webdav.

Webdav publishing

Make sure you don't have Webdav publishing installed, as it may interfere with Sense/Net webdav features.

Opening a document library in Windows Explorer

Please note, that this feature works with Internet Explorer versions prior to 11 only.

To open a Sense/Net document library in Windows Explorer navigate to the document library and select the Open in Windows Explorer action from the Actions menu:

Opening a document library via webdav

The contents of the document library will appear as folders and files opened in Windows Explorer:

Opening a document library via webdav

Opening Office documents

Managing workspace documents using Microsoft Office is a common feature of Enterprise Content Management Systems. Using Sense/Net you are able to create, modify or delete workspaces within Office. Opening and saving documents is also done using the webdav protocol. To open a document click the Edit in Microsoft Office action on the document:

Opening Office documents via webdav

For more info on managing Office documents in the Sense/Net Content Repository within Microsoft Office please read the following article:

Mapping the Content Repository to a network drive

It is also possible to map the full Sense/Net Content Repository to a network drive. To do this first click the Map network drive... link on the Computer in the Windows Start menu:

Mapping Sense/Net to a network drive

Select a suitable drive letter and enter the web address of your Sense/Net site:

Mapping Sense/Net to a network drive

After clicking Finish the Content Repository should appear in Windows Explorer:

Mapping Sense/Net to a network drive

From here onwards you can use this drive to manage your Content Repository: uploading, editing, deleting, renaming content can be done just like using a normal file system.

Uploading different file types

The Sense/Net Content Repository is much more than a simple file system. It can distinguish between different file types. An image for example in a regular file system is a simple file with .png or .jpg extension, an image in the Sense/Net Content Repository however is an content of Image type, which is derived from the File type. Therefore when using the Content Repository via webdav it is desired to make connections between files with different extensions and Content Repository types. This is done with the same web.config setting that is used by the upload function on the ui:

<sensenet>
  <uploadFileExtensions>
    <add key=".jpg" value="Image"/>
    <add key=".jpeg" value="Image"/>
    <add key=".gif" value="Image"/>
    <add key=".png" value="Image"/>
    <add key=".bmp" value="Image"/>
    <add key=".xaml" value="WorkflowDefinition"/>
  </uploadFileExtensions>

For example when dropping a file with .png extension the content created in the Sense/Net Content Repository will be of Image type.

Configuration

The configuration for webdav can be found in the web.config under the webdavSettings section:

<sensenet>
  <webdavSettings>
    <add key="MockExistingFiles" value="desktop.ini,Thumbs.db,wdmaud.drv,foo,MSGRHU32.ini"/>
    <add key="WebdavDefaultPageTemplate" value="Internet_Page.html"/>
  </webdavSettings>

The following options can be set:

  • MockExistingFiles: some versions of webdav clients shipped with Windows will automatically probe on certain files and will fail to continue if those files are not present. Since these files are never present in a Sense/Net Content Repository, the webdav handler mocks these files as if they existed there to ensure flawless operation. These files may vary from system-to-system, so if you experience any problems with opening Sense/Net Content Repository folders via webdav it is possible that your webdav client is looking for files not present in the Content Repository. Use fiddler or a debug version of Sense/Net with dbgview to detect this situation and extend this list with the file names to be mocked as existing.
  • WebdavDefaultPageTemplate: if you upload an aspx file the pagetemplate of the created Sense/Net Page will be the one specified with this option.

Custom WebDav provider

It is possible to customize the behavior of the WebDav feature by developing a custom provider. Developers can restrict what users see in Windows Explorer and what they can do with files and folders.

Example/Tutorials

There are no examples for this article.

Related links

References

There are no external references for this article.