Search: none
Add a search phrase to search resource page titles and descriptions. Different keywords are ANDed with tags.
 

MSDN Archive

Target and filter your gallery search using the following dynamic dialogues.
1-7 of 7Resources < Previous 1 Next >
Resource Page Name and Description Current Release
This tool allows to verify if the feature definition files for all installed features are present on the file system. Also allows to verify if the features used in site collections an sites are ins...
This tool allows to verify if the feature definition files for all installed features are present on the file system. Also allows to verify if the features used in site collections an sites are installed on the server. In addition it can create a checklist file which can be used to verify if a server has all features installed required to act as destination for a content deployment job of an existing sitecollection. Usage: WssAnalyzeFeatures -url http://server:port This command will verify all features on the server and in the site collection. It will create two files: - ProblemFeatures.txt outlining all identified problems. - ContentDeploymentFeatures.txt this is the created checklistfile. It will contain all features that have to exist on the target to be able to act as target for a content deployment of the site collection. WssAnalyzeFeatuers -verify ContentDeploymentFeatures.txt this command will verify the features installed on the server against the features listed in the ContentDeploymentFeatures.txt checklistfile which was created on the source server.
Popular tags: WSS, Tools, MOSS
Downloads: 43 | Started: Apr 12 2008  | Contributors: 1
WssAnalyzeFeatures
Apr 12 2008
Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server 2007 support a rich security model that allows administrators to control access to sites and content by assigning permissions ...
Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server 2007 support a rich security model that allows administrators to control access to sites and content by assigning permissions to users and groups for a specific securable object (such as site, list, library, folder and even an individual document or item). However, in certain scenarios there is a need to secure access to individual columns in lists or document libraries. Currently, SharePoint does not provide out of the box support for securing columns or views. A typical scenario that would require this might be a list that contains a broad spectrum of information about an employee or a client, where certain columns (salary, revenue to date, potential to promote, etc.) might ideally only be viewable by certain groups within the portal. To address those scenarios, this paper describes a method to leverage SharePoint extensibility and built-in item to level security to allow applying column-level permissions to a custom field type. This is accomplished through the use of a lookup field as the column, with behind the scenes ties to another list that contains the secure values and a method to provision those values back to the lookup only for users with valid permissions. The result is that in the view mode authorized users will see the content of a secure column as if it was a normal column, while unauthorized users will not see the content of the column at all. This different behavior is shown in Figure 1. Similarly, only authorized users will be able to access the content of a secure column in new and edit modes.
Popular tags: security, SharePoint, Custom Field Type, MOSS, WSS
Downloads: 32 | Started: Jul 11 2008  | Contributors: 2
SecureField 1.0
Nov 10 2008
FIX: Out of the box TFS requires Windows Sharepoint Services 2.0, installed on the AT box. There is a mechanism to allow installing WSS 2.0 on a box other than the AT box, but as of now WSS 3.0 is ...
FIX: Out of the box TFS requires Windows Sharepoint Services 2.0, installed on the AT box. There is a mechanism to allow installing WSS 2.0 on a box other than the AT box, but as of now WSS 3.0 is not supported. This fix provides WSS 3.0 support to the current version of TFS.
Downloads: 21 | Started: Apr 15 2008  | Contributors: 2
KB932544
Jun 18 2007
In some situation the STSADM command STSADM.EXE -o deactivatefeature is not able to deactivate a feature either on site collection or on site level. This can (e.g.) happen if the feature definition...
In some situation the STSADM command STSADM.EXE -o deactivatefeature is not able to deactivate a feature either on site collection or on site level. This can (e.g.) happen if the feature definition for the feature that has to be removed is not installed in the farm. This tool allows to remove the feature from the site or site collection completly. Usage: WssRemoveFeatureFromSite -scope (site|sitecollection) -url <url-to-site> -featureid <featureid> -force
Popular tags: WSS, MOSS, Tools, SharePoint
Downloads: 13 | Started: Apr 12 2008  | Contributors: 1
This is sample code demonstrating how one could integrate an external content repostory with SharePoint, in a way such that the external repositories may participate in MOSS workflows, utilize task...
This is sample code demonstrating how one could integrate an external content repostory with SharePoint, in a way such that the external repositories may participate in MOSS workflows, utilize tasks lists, and extensible metadata.
Popular tags: WSS, CMIS, Content Management, SharePoint
Downloads: 10 | Started: Jan 13 2009  | Contributors: 2
This sample code accompanies the MSDN technical article, "Building and Distributing Workflows in SharePoint Products and Technologies for Use in Customer and Partner Environments" (http://msdn.micr...
This sample code accompanies the MSDN technical article, "Building and Distributing Workflows in SharePoint Products and Technologies for Use in Customer and Partner Environments" (http://msdn.microsoft.com/en-us/library/cc511934.aspx) by David Mann. In this article, you can learn about the steps that are necessary to successfully deliver a workflow in a customer or partner environment using SharePoint Products and Technologies. Writing and supporting software that is intended to run in a customer’s or partner’s environment can be a somewhat scary prospect. Lack of control, disparate environment specifications, unknown end users, and lack of direct interaction are just a few of the potential issues that you must deal with. For independent software vendors, or ISVs, these issues are a fact of life. This is just one more item to be concerned about when they introduce workflow into their application. The article does not deal directly with the basic process of building and deploying a workflow. Instead, it focuses on the extra steps necessary to successfully deliver a workflow into a customer or partner environment. The goal of the article is to make you think about workflows differently: to think about them as part of your product or application—not as an afterthought. The article raises many issues, gives you a lot to think about, and points out some (not all) possible paths to a solution. The final direction you take depends on your application, your company, and your clients.
Downloads: 4 | Started: May 28 2008  | Contributors: 1
Sample code
May 28 2008
Site Source is a Word 2007 add-in that displays a custom ribbon and a custom task pane that allow the user to connect to a Windows SharePoint Services list directly from the Word client and insert ...
Site Source is a Word 2007 add-in that displays a custom ribbon and a custom task pane that allow the user to connect to a Windows SharePoint Services list directly from the Word client and insert data from the list without using the clipboard.
Popular tags: Addin, C#, C# 3.0, LINQ, LINQ to XML, OBA, Office 2007
Downloads: 3 | Started: Mar 24 2008  | Contributors: 1
Updating...
Page view tracker