Microsoft Sharepoint Products and Technologies Resource Kit eBook

The SharePointPermission Class
Chapter 33: The Windows SharePoint Services Object Model 933
This code example uses the SharePointPermission class, which represents a custom
permission that controls the ability to access Microsoft SharePoint Products and
Technologies resources. The SharePointPermission class cannot be inherited.
The constructor of the SharePointPermission class expects, like all code-access
permission objects, a System.Security.Permissions.PermissionState enumeration value.
This value represents a value specifying whether an entity, at creation, should have
full or no access to resources. This value can be set to None to indicate that a
new instance is fully restricted or Unrestricted. Next the code example accesses
the UnsafeSaveOnGet property of the SharePointPermission class to get a value
indicating whether saving to the SharePoint Products and Technologies database
is allowed during an HTTP-GET request. Because this code example uses the
PermissionState.Unrestricted value, it will return True.
SharePointPermission myPermission = new SharePointPermission(PermissionState
.Unrestricted);
output.Write(myPermission.UnsafeSaveOnGet);
Note You can copy this code into the RenderWebPart method of a Web
Part. Remember to import the Microsoft.SharePoint.Security namespace.
Microsoft.SharePoint.SoapServer Namespace
The Microsoft.SharePoint.SoapServer namespace contains classes that implement
the Windows SharePoint Services Web Service on the server. This namespace can be
found in the Windows SharePoint Services assembly (in Microsoft.SharePoint.dll).
The numerous methods provided by the Windows SharePoint Services Web service
are designed for accessing content on a site, including methods for working with
lists or site data, as well as methods for customizing meetings, imaging, Document
Workspace sites, or search. In most cases, the members of these classes are not
designed to be called from the server and are not tested in this configuration. The
methods provided by a Web service are designed to be called remotely from client
applications. An excellent example of client applications that use the Web services
provided by the Microsoft.SharePoint.SoapServer namespace is Office 2003 itself.
The Simple Object Access Protocol (SOAP) interfaces used in these services
provide .NET developers with object models for creating solutions that work with
Windows SharePoint Services remotely from a client or custom application. The interfaces
are integrated with the server-side object models of the Windows SharePoint
Services assembly, and their design has been optimized to reduce the number of
roundtrips transacted between client computer and server.