One cool feature available in the new generation of SharePoint services, is the Health Analyzer. I’m not quite sure how this has been implemented internally but it’s a part of the new Monitoring section in Central Administration.
SharePoint Foundation: Installing the Prerequisites November 18, 2009
I couldn’t help posting a quick article tonight. I’ve decided to install SharePoint Foundation first, before installing SharePoint Server 2010. The reason I went down this path is that SPF interests me a lot more that SharePoint itself. I’m really keen on playing with the new APIs and working through the SDK.
SharePoint 2010 Public Beta Released for Download November 18, 2009
The SharePoint 2010 Public Beta has been released for download to MSDN subscribers. I’m in the process of downloading the beta and I’ll start blogging again.
I’ve been away from this site for a while, but I really want to focus on blogging about all the new cool features in WSS4 (a.k.a. SharePoint Foundation) and SharePoint 2010.
I’ve upgraded my laptop to 8GB RAM and I’ve got a Windows\SQL 2008 virtual machine ready to install onto.
So, please stay tuned for new content.
I haven’t visited this site in a couple of months now. I’m quite surprised to find that I’m still averaging between 100 and 170 hits per day. Thanks to everyone that’s visiting.
Please drop me a G’Day in the comment boxes!
Speak soon.
P.S. If you’re a developer, check out the SharePoint 2010: Professional Developer Evaluation Guide and Walkthroughs Microsoft’s made available as a free download. It gives an overview of some of the types of solutions developers can expect to build with SharePoint 2010 and then gives six walkthrough examples. Also, the SharePoint 2010 SDK already has some great content.
-fodi
70-541: Create an Action to Add an Option to the Site Settings Menu May 19, 2009
Short & Sweet
Actions in SharePoint are links that you can add at various areas of a site. They are deployed using features and allow you to add hyperlink entries to areas such as: The Site Actions drop-down, the Site Settings page, a list’s toolbar menu and a list item’s ECB menu.
Define a custom action by using the CustomAction element within an elements manifest file. The Title attribute is the only required attribute. To define the Url add a child element named UrlAction and set its Url attribute.
Detailed Information
(more…)
70-541: Localize a feature using a resource file April 11, 2009
Short & Sweet
Resource files allow you to expose strings used by you applications. WSS supports two types of rerource files: provisioning and run-time. The former is used by features and solutions. The latter is used by ASP.Net. Provisioning resource files are stored in your feature’s Resources folder (by default) unless you either specify a DefaultResource file in feature.xml or reference the resource file with a three-part reference. Run-time resource files are stored in App_GlobalResources for the application and they’re copied there from ~12CONFIGRESOURCES when the web application is first deployed. Run-time resources are always referenced with their three-part name.
Detailed Information
70-541: Specify an Event Receiver to handle events for a feature April 8, 2009
Short & Sweet
SharePoint comes with four types of feature receivers: FeatureActivated, FeatureDeactivating, FeatureInstalled & FeatureUninstalling. They are made available as overridable methods, if you implement the SPFeatureReceiver class, which is a part of Microsoft.SharePoint.dll.
You can attach your assembly to a feature, by adding two attributes to the <Feature> element of its feature.xml file. Provide the 4-part assembly name to the ReceiverAssembly attribute and the class name to the ReceiverClass attribute.
Detailed Information
70-541: Specify a feature that depends on another feature to activate April 4, 2009
Features support activation dependencies, meaning that the feature will only activate if a dependant feature is already active.
Short & Sweet
In the feature.xml file, add an ActivationDependencies element. Within this element add an ActivationDependency element for each feature that your feature depends on. Reference these features by their GUID. In certain circumstances dependant features will automatically be activated and deactivated.
Detailed Information
70-541: Deploy a user control so that it can be used by any Windows SharePoint Services component April 4, 2009
A user control consists of two files: the .ascx file and the .dll file.
Short & Sweet
- Place the .ascx file in the ~\12\CONTROLTEMPLATES folder
- Place the .dll in either the GAC (and reset IIS) or the \bin folder (and modify security policies)
- Add a SafeControl entry in Web.config.
Detailed Information
70-541: Deploy a Web service to a Windows SharePoint Services front-end Web server April 4, 2009
Web services are deployed to the _vti_bin folder of a site collection. This folder is virtualised by IIS and actually maps to the ~\12\ISAPI folder on the filesystem.
Short & Sweet
Copy the *wsdl.aspx, *disco.aspx and *.asmx files to the ~\12\ISAPI folder. To make them discoverable to Visual Studio, add a reference to the disco and wsdl files in ~\12\ISAPI\spdisco.aspx.
Detailed Information
70-541: Install and activate a feature by using STSADM April 4, 2009
I explained this process in the previous 70-541 post, but I’ll add it here for completeness and try to add a bit more information.
Short & Sweet
Installing a feature adds it to the site catalogue. Activating it enables its functionality. stsadm supports both processes:
- To install a feature use stsadm’s installfeature command:
stsadm -o installfeature -name MyFeatureName - To activate a feature use stsadm’s activatefeature command:
stsadm -o activatefeature -name MyFeatureName -url http://MySiteCollection
Detailed Information
