I am a very big fan of Content Editor Webpart in Moss 2007. I have done many site customization's using CEWP in SharePoint 2007. Place a new html file, hack DOM elements using JQuery and modify the html elements, javascript etcs., I almost love it. Even I have developed a complete site using few CEWP's in SharePoint 2007.
I was hoping SharePoint 2010 would offer much more functionality to CEWP. But to the sad part it has worsened it usability. When I first tried inserting a CEWP in my SharePoint 2010 site, I virtually struggled to use it. I was trying to figure our how to insert my custom html. There was no Source editor in WebPart editor panel.
Edit Html source has been moved to the Ribbon. You have to click the "HTML-EditHTMLSource" and place your html.
And the worst part is now you cannot place any javascript code in the source editor(edit html source).
To place a javascript code you need to create a text file or html file and put your code there. Save it to some document library and link the file as show below in the editor pane
I like it in one way. We can checkin the code in Source control and deploy the text file or html file to the layouts folder and we can link it in our webpart so that we can have a backup of the code.
Saturday, July 16, 2011
Friday, July 15, 2011
Custom Workflow Activity for SharePoint Designer 2010
Back in Moss 2007 we had the feature of creating a new custom activity for SharePoint designer. I never tried that. Yesterday I had to present a POC to a customer on Custom activity for SharePoint designer 2010. The requirement is pretty simple.
User will be presented with a simple list. On creating of a new item, a approval workflow will be triggered. On approval, a new subsite has to be created. So I thought creating a custom activity in designer and using that to create a designer workflow would to do the trick.
I will describe with steps to create a custom activity for a SharePoint designer 2010 below. Since creating a approval workflow is simple I m not going to cover it :-)
1. Open Visual Studio
2. Select the “File->New->Project”
3. For template, select “Workflow->Workflow Activity Library” ( If you don't see this template, then target your environment to .Net 3.5.)
4. For Name, type “CustomActivities”
7. Rename Activity1.cs to CustomAction.cs
8. Right click the project, select “Add Reference”
9. Add the following references:
o C:\program files\common files\microsoft shared\web server
extensions\14\isapi\Microsoft.SharePoint.dll
I dont want to jump into full code directly. Lets go Step by Step.
Create a new function which creates new site
To make your custom code we need to override the Execute method of System.Workflow.Activities.
Call our CreateSite() function within the Execute method.
We have created a simple activity which is good enough to create a new SharePoint site. But if you notice I have hardcoded the siteTitle and siteURLRequested. Not good practice ah..
Lets create a new set of properties to get and set values for our title and url parameters. Before that to make the properties to be picked by the SharePoint designer we need to create Dependency properties as below.
public static DependencyProperty TaskTitleProperty = DependencyProperty.Register("TaskTitle", typeof(string), typeof(CustomAction));
[Category("Cross-Site Actions"), Browsable(true)]
[DesignerSerializationVisibility
(DesignerSerializationVisibility.Visible)]
public string TaskTitle
{
get
{
return ((string)
(base.GetValue(CustomAction.TaskTitleProperty)));
}
set
{
base.SetValue(CustomAction.TaskTitleProperty, value);
}
}
Note that we need to prefix the DependencyProperty with the word "Property" else VS2010 is going to shout at you.
Now use the dependency property created in our CreateSite method. Overall code looks like below.
So create another dependency property for siteUrlRequested as well which i m not doing here. Sign the assembly and build it. Place the assembly in GAC using gacutil.exe(never install manually).
We are done with the coding part. Now lets register our newly created activity with the SharePoint designer.
If you navigate to 14 hive folder under 1033/Workflows/ you will find MOSS.ACTIONS and WSS.ACTIONS.
As a good housekeeping we will create a new ACTIONS file. Say CustomAction.ACTIONS.
Place the below xml in it to register our custom activity.
User will be presented with a simple list. On creating of a new item, a approval workflow will be triggered. On approval, a new subsite has to be created. So I thought creating a custom activity in designer and using that to create a designer workflow would to do the trick.
I will describe with steps to create a custom activity for a SharePoint designer 2010 below. Since creating a approval workflow is simple I m not going to cover it :-)
1. Open Visual Studio
2. Select the “File->New->Project”
3. For template, select “Workflow->Workflow Activity Library” ( If you don't see this template, then target your environment to .Net 3.5.)
4. For Name, type “CustomActivities”
7. Rename Activity1.cs to CustomAction.cs
8. Right click the project, select “Add Reference”
9. Add the following references:
o C:\program files\common files\microsoft shared\web server
extensions\14\isapi\Microsoft.SharePoint.dll
I dont want to jump into full code directly. Lets go Step by Step.
Create a new function which creates new site
To make your custom code we need to override the Execute method of System.Workflow.Activities.
Call our CreateSite() function within the Execute method.
We have created a simple activity which is good enough to create a new SharePoint site. But if you notice I have hardcoded the siteTitle and siteURLRequested. Not good practice ah..
Lets create a new set of properties to get and set values for our title and url parameters. Before that to make the properties to be picked by the SharePoint designer we need to create Dependency properties as below.
public static DependencyProperty TaskTitleProperty = DependencyProperty.Register("TaskTitle", typeof(string), typeof(CustomAction));
[Category("Cross-Site Actions"), Browsable(true)]
[DesignerSerializationVisibility
(DesignerSerializationVisibility.Visible)]
public string TaskTitle
{
get
{
return ((string)
(base.GetValue(CustomAction.TaskTitleProperty)));
}
set
{
base.SetValue(CustomAction.TaskTitleProperty, value);
}
}
Note that we need to prefix the DependencyProperty with the word "Property" else VS2010 is going to shout at you.
Now use the dependency property created in our CreateSite method. Overall code looks like below.
So create another dependency property for siteUrlRequested as well which i m not doing here. Sign the assembly and build it. Place the assembly in GAC using gacutil.exe(never install manually).
We are done with the coding part. Now lets register our newly created activity with the SharePoint designer.
If you navigate to 14 hive folder under 1033/Workflows/ you will find MOSS.ACTIONS and WSS.ACTIONS.
As a good housekeeping we will create a new ACTIONS file. Say CustomAction.ACTIONS.
Place the below xml in it to register our custom activity.
<WorkflowInfo> <Actions Sequential="then" Parallel="and"> <Action Name="Create Site" ClassName="CustomActivities.CustomActions" Assembly="CustomActivities, Version=1.0.0.0, Culture=neutral, PublicKeyToken=a3170baa21b0a3e9" AppliesTo="all" Category="Custom Site Actions"> <RuleDesigner Sentence="Create a Site titled %1"> <FieldBind Field="TaskTitle" DesignerType="TextArea" Id="1"/> </RuleDesigner> <Parameters> <Parameter Name="TaskTitle" Type="System.String, mscorlib" Direction="In" /> </Parameters> </Action> </Actions> </WorkflowInfo>Save the file and close. We have a very last step that to register our dll as a Authorized type with my webapplication. Navigate to web.config in the file system and make the below entry.<authorizedType Assembly="CustomActivities, Version=1.0.0.0, Culture=neutral, PublicKeyToken=a3170baa21b0a3e9" Namespace="CustomActivities" TypeName="*" Authorized="True" />Save the web.config. There you go..Perform and IISReset and load the designer. You will see a new activity added under "Custom Site Actions"
Saturday, June 11, 2011
What does IISReset really do
IISReset- perhaps the first lesson every SharePoint developer and administrators learn.
But when we start to do extreme programming(really lol), we eventually forget to do this.. cool lemme come to the meat of the subject..
Last week I have to support from development side for a uat deployment of our new solution. Every thing worked well in my environment as always. My development environment is a standalone farm. testing, uat and prod are medium farms..
We deployed the code. loaded the site..Some code error..ahhh.. i could see clearly from the error that the new code is not referred by the page. We did redeployment as I insisted confidently that Web hosting team didn't do the deployment as I specified in the install notes. Whenever something go wrong then its other mistake. lol...
So we deployed the solution..again same error. Now Web hosting team hit me back stating its my error.
on multiple refresh of the page, i saw the site loading correctly on few instances. ahhhh i caught the culprit. "DLL caching". I asked to do IISReset on all the WFE's. It worked.
So whats the issue.
Whenever we deploy a new code which has a dll we probably need to do a IISReset.
You know why, SharePoint when hosted in IIS caches the dll from GAC and renders the page from it. So we have to tell the GAC to take the new dll from GAC after new deployment of our code.
Do we need to do IISReset on all new deployment. Answer is no.
1. When we do partial trusted solution SharePoint automatically picks up the new dll from the bin. We dont need an IISReset.
2. When we deploy features, we dont need it unless and until it doesn't has any code.
Most of the prod servers doesn't allow us to do IISReset. Then how to tell my IIS to take the new dll from the GAC.
Use the below script to refresh the application pool.
But when we start to do extreme programming(really lol), we eventually forget to do this.. cool lemme come to the meat of the subject..
Last week I have to support from development side for a uat deployment of our new solution. Every thing worked well in my environment as always. My development environment is a standalone farm. testing, uat and prod are medium farms..
We deployed the code. loaded the site..Some code error..ahhh.. i could see clearly from the error that the new code is not referred by the page. We did redeployment as I insisted confidently that Web hosting team didn't do the deployment as I specified in the install notes. Whenever something go wrong then its other mistake. lol...
So we deployed the solution..again same error. Now Web hosting team hit me back stating its my error.
on multiple refresh of the page, i saw the site loading correctly on few instances. ahhhh i caught the culprit. "DLL caching". I asked to do IISReset on all the WFE's. It worked.
So whats the issue.
Whenever we deploy a new code which has a dll we probably need to do a IISReset.
You know why, SharePoint when hosted in IIS caches the dll from GAC and renders the page from it. So we have to tell the GAC to take the new dll from GAC after new deployment of our code.
Do we need to do IISReset on all new deployment. Answer is no.
1. When we do partial trusted solution SharePoint automatically picks up the new dll from the bin. We dont need an IISReset.
2. When we deploy features, we dont need it unless and until it doesn't has any code.
Most of the prod servers doesn't allow us to do IISReset. Then how to tell my IIS to take the new dll from the GAC.
Use the below script to refresh the application pool.
Option Explicit
'*** spsapppoolrecycle.vbs
'*** Script to recycle Sharepoint Portal Server application pool
'*** For use when deploying updated version of Webparts in the GAC
'*** Author: Michael Christensen, mac@landscentret.dk
'*** Provided AS IS with no warranties
'*** Heavily based on this posting by David Wang:
'*** http://tinyurl.com/4k26n
Const WEBSITEID = 1
Dim objApp
Dim AppPoolId
Dim objAppPool
Set objApp = GetObject("IIS://localhost/w3svc/" & WEBSITEID & "/root")
AppPoolId = objApp.AppPoolId
WScript.Echo "AppPoolID: " & AppPoolId
Set objAppPool = GetObject( "IIS://localhost/w3svc/AppPools/" + AppPoolId )
objAppPool.Recycle()
WScript.Echo "AppPool recycled."
The script assumes that Sharepoint is installed on the virtual server with ID 1. This will usually be the case, otherwise the actual ID could probably be determined programmatically.
Probably next time when you deploy the new code,,think whether is necessary to do an IISRESET after deployment.
Saturday, May 14, 2011
Blank SharePoint Site in Windows 7
Another issue with SharePoint 2010 installation in Windows 7. When I create a new site collection through central administration and browse through the page, it shows a blank page. Even sometimes I receive the blank page when I open Central administration. Weird :-(
After doing many changes and I have even reinstalled the farm to get rid of this issue. No luck. After a long time I found the issue is with the authentication.
to make the sites to work do the following.
1. go to IIS : cmd-inetmgr.
2. Go to your site collection.
3. Click Authentication
4.Right click Basic authentication and enable it.
5. There you go..refresh the page..you will see you sites.. bravo..
After doing many changes and I have even reinstalled the farm to get rid of this issue. No luck. After a long time I found the issue is with the authentication.
to make the sites to work do the following.
1. go to IIS : cmd-inetmgr.
2. Go to your site collection.
3. Click Authentication
4.Right click Basic authentication and enable it.
5. There you go..refresh the page..you will see you sites.. bravo..
cannot connect to configuration database
I have installed SharePoint 2010 in Windows 7. I had to do many configuration changes to make it work. Not excited though. It should work in the same way as it should have in Windows server. Whenever i turn off my system, start again and broswe to anysites or central admin I receive this error.
"cannot connect to configuration database"..
very annoying ah?..
The reason is everytime you turn off you system, the SQL Server(SharePoint) services also get stopped.
To make the sites to work normally go to Services.msc and make sure the following services are running. If not right click and start it.
1. SQL Server (MSSQLSERVER)
2. SQL Server (SHAREPOINT)
"cannot connect to configuration database"..
very annoying ah?..
The reason is everytime you turn off you system, the SQL Server(SharePoint) services also get stopped.
To make the sites to work normally go to Services.msc and make sure the following services are running. If not right click and start it.
1. SQL Server (MSSQLSERVER)
2. SQL Server (SHAREPOINT)
Thursday, April 14, 2011
Personal sites(MySite) configuration in SharePoint 2007
The first thing you should do is make sure you’ve created a Shared Service Provider (SSP). To check this do the following:
- Go to MOSS 2007 Central Administration
- Click on Shared Services Administration in left navigation
- If this list is not empty then click on an SSP
- If this list is empty then click New SSP and create a Shared Service Provider
Once on the Shared Services Administration page for your SSP you should see at least 3 sections titled: User Profiles and My Sites, Audiences and Search. To get started you’ll need to import user profiles from the directory.To import user profiles:
- Under User Profiles and My Sites click on the link labeled “User profiles and properties”
- On the User Profiles and Properties page click on “Configure profile import”
- Provide a default access account, specify an account that has read access to your directory.Note: This account needs to also have Manage User Profiles rights, verify click on “Personalization services permissions” under User Profiles and My Sites on the SSP Admin page. To keep things simple until you have a grasp of the service you should use the SharePoint Admin account.
- Click OK
- On the User Profiles and Properties page click on “Start full import”
- Verify that import started and wait until import has completed before moving on to other personalization admin tasks (this may take a few hours)
- After import is complete to view the results click on “View user profiles” on the User Profiles and Properties page
The SSP administrative portion of My Site should have been configured when you created the SSP. So while waiting on profile import to complete you can explore the non administrative parts of My Site.To create a My Site:
- Click on My Site in the global actions bar which is in the top right corner of every SharePoint page
- Wait while your My Site is created
- After creation is complete check to make sure the name of the site created is titled with your name
- If not then open a new browser window with your credentials and click the My Site link again or copy the URL behind the My Site link into the browser window.Note: My Site is highly personalized so it works best when its created using your credentials and not those of an admin account or alternate account
- Follow the links in the Getting Started with My Site web part
Once profile import is complete we can go back to setting up personalization services in the SSP Admin page. Now that we have profiles we can do things with them like create audiences.To create audiences:
- Go to the Shared Services Administration page for your SSP.
- Click on “Audiences” under the section Audiences
- On the Manage Audiences page click on “Create audience”Note: Audiences should not be created until after you’ve completed a profile import.
- Walk through the steps to create a new audiences based on user profile data
- After you’re done creating audiences click on “Start compilation” from the Manage Audiences pageNote: Audiences must be compiled before they can be used.
- After compilation is complete to view the results click on “View audiences” from the Manage Audiences page
Now that we have created new audiences we should put them to use on SharePoint sites by targeting content. To target content on SharePoint sites:
- Go to SharePoint site
- Go to the document library on the site
- Go to Document Library Settings
- Click on “Audience targeting settings” under General Settings
- Enable audience targetingNote: You can do this for any list type not just documents.
- Go back to the document library
- Edit or upload a new document
- Click the Browse button in the Target Audiences field
- Select an audience you created or search and use an existing distribution listNote: Distribution lists and security groups will only display after you’ve completed a profile import.
- Click OK to update the document’s properties
To display targeted content on SharePoint sites:
- Go to the site home page and add the Content Query Web Part
- Modify the Content Query Web Part
- Under Query change List Type to Document Library
- Under Query -> Audience Targeting check “Apply audience filtering”
- Click OK
- Verify the items you targeted in the document library only show for people in those audiences.
Now that you’ve had a chance to see how audience targeting works let’s move on to People Search. To setup people search:
- Go to Shared Services Administration for your SSP
- Under Search section click on “Search settings”
- On Configure Search Settings page find the default content access account
- If this is not set then provide a default content access account
- Verify default content access account has Use personal features rightsNote: To verify click on “Personalization services permissions” under User Profiles and My Sites on the SSP Admin page. To keep things simple until you have a grasp of the services you should use the SharePoint Admin account.
- On Configure Search Settings page click on “Content sources and crawl schedules”
- On the Manage Content Sources page hover over “Local Office SharePoint Server sites” and click the arrow to drop the ECB menu
- In the drop menu click Start Full Crawl
- Verify that crawl started and wait until crawl has completed before moving on to search for people
Finding people:
- Once crawl is complete to main portal site and click on Search in the top navigation area to go to the Search Center
- In Search Center click on tab labeled “People”
- Type in a term you added to your profile while exploring your My Site such as a project, skill or responsibility
- Hit Enter or click the Go button
- Verify that you and others who match that search term was returned as search results
One area of personalization we haven’t touched on at all yet is publishing links to the Office client. Links to SharePoint lists, libraries, and sites can be published to Office 2007 clients as places to easily retrieve or save documents. To publish links to Office 2007 clients:
- Go to Shared Services Administration for your SSP
- Under User Profiles and My Sites click on “Published links to Office client applications”
- Click New to add a link
- Provide a URL, name and type for the link
- If you want to the link to only show for a specific set of people then specify and audience
- Click OK
To view links in the Office 2007 client:
- Open Word 2007
- Open the File Open or Save As dialog box
- Click on My SharePoint Sites on the leftNote: In order for the service to find the SSP you must set the My Site you created earlier as your default My Site.
- Verify link are presented
Configure SharePoint 2007 search to display results based on Custom profile properties.
SharePoint search is very powerful feature which is not used to its full extent often. Many of SharePoint farms use custom user profile properties, but doesn't get configured to return search result based on this meta data.
Below are the step by step description how to configure custom user profile properties in search.
Now lets configure this property in the SSP so that based on this property search can be performed.
Note: The newly added user profile properties should contain value to be crawled by Search service.
Below are the step by step description how to configure custom user profile properties in search.
- Create a custom user profile property. Go to Central admin-SSP-User profiles and properties.
- View user profile profiles-click add a new user profile property.
- Give a name to it and type of value, check the 'Indexed' box.
- Privacy setting can be anything(everyone or only me). Many articles suggest this to be configured as everyone to display in the search. But it really doesn't matter. Whatever the privacy setting once you check the 'Indexed' checkbox the property will be crawled by the search service.
Now lets configure this property in the SSP so that based on this property search can be performed.
- Go to SSP-Search Administration
- Click Managed Properties.
- Newly created user profile property has to be included here so as to make indexing service crawl this property.
- Click add a new property.
- Give any name for the propery(not to make complex name the same as your profile property).
- Select 'Include values from all crawled properties mapped'.
- Click Add Mapping. Under Crawled properties you should see your new user profile properties.
- Most commonly you would not see you newly added user profile property here. To do so start a incremental crawl for the content source.
- Now go back to your Crawled properties, you will see your custom property. Select it and map it to the new meta data propery.
- Click ok.
- Do a full crawl.
- Now you can perform search based on the custom user profile property added. To verify easily. Go to your mysite. Click Edit profile. You will see the new added property. Click on its value. It should redirect to the search page with the results.
Note: The newly added user profile properties should contain value to be crawled by Search service.
Subscribe to:
Posts (Atom)



