Some SharePoint 2010 findings

While going through some business requirement analysis for SharePoint 2010 I came across these useful resources that I think are worth sharing as they focus on specific topic’s under consideration.

Blog Customization

Display recent changes
SharePoint 2010 profile customisation and integration with other systems

Authentication methods

IBM websphere integration

Sending update Notifications to Email Distribution group

It is possible to send document updates to members of a email distribution list
in two main ways
1) Alerts for the documents and lists, and putting the distribution list and the to source
2) Create a work flow and automate it to send out updates to a distribution list
“Instead of Security Groups, it’s possible to just have some custom SharePoint groups with users in them, and this could be managed by the site admin or individual owners of each group could be given control of their respective groups.  These groups could be referenced in an SPD workflow based off metadata within the submitted doc.  So, let’s say someone submits a doc and selects “Finance” in a department dropdown.  The workflow would kick off, read the Finance metadata from the Department field, and then send the email to the SharePoint Group that you specify for any Finance-related doc.  You’d have to do your mapping in SPD with conditions (If Finance, then send email to Finance Leadership Team).  This is one way to do it without code, but there are other ways.  It just depends on the exact requirements and tools available.”
It is also possible to Sync SharePoint AD Groups with Distributionlist, however not vise versa.
It is also possible to send out emails to Documents and Lists within SharePoint
SharePoint 2010 browser and office compatibility



Enhanced by Zemanta

Changing External URL to SharePoint 2010 (Alternate Access Mapping)

I installed the public demo of SharePoint 2010 right after its release on a Virtual box based Windows 2008 64 bit install. Although the documentation suggests that one needs at least 4 GB of memory but I am running this install on a VM configuration of around 2 GB and it is working smooth for me.

For a client demo we released that some URLs for the external access to the SharePoint install were being redirected to the internal URL, hence those pages did not work for external access. After 5 minutes of effort I found out that it’s a very simple configuration in the central administration at Central Administration – > Alternate Access Mapping, that allows one to provide an external facing URL to the SharePoint install.

The main point to note over here, is that my experience with SharePoint 2010 has been a very pleasant one, its relatively easy to find what you are looking for, and over all look and feel of not only the front end but admin section has been simplified, which provides an excellent user experience.

Enabling Sharepoint Intellisense in Visual Studio 2008

Styling Sharepoint sites depends heavily on creating and editing XML files that need to follow sharepoint schema.

the first thing to note is if WSS (Windows Sharepoint Services) are installed on the same machine as you Visual Studio on not, Microsoft suggests to develop Sharepoint application on a windows server 2003, so that debugging and testing is facilitated.

If Visual Studio is on the WSS machine then all you need to do is create a xml file e.g sharepoint.xml in the folder Program Files\Microsoft Visual Studio 9.0\Xml\Schemas

Place the following code in it

<SchemaCatalog xmlns="">
<Schema href="%CommonProgramFiles%/Microsoft Shared/web server extensions/12/TEMPLATE/XML/wss.xsd" targetNamespace="" />

Restart Visual Studio and add the following line to your top most element xmlns="" in your XML file this should enable intellisense in your XML file.

For Environments where WSS is not installed on the same machine, wss.xsd file can be copied to the development machine and the above code altered to point to the xsd file location.