Sunday, September 26, 2010

Find some nice video regarding SharePoint 2010

http://channel9.msdn.com/Tags/devdays-2010-nl?sort=viewed&page=4

http://channel9.msdn.com/learn/courses/SharePoint2010Developer/

Upgrading your Content Database to SharePoint 2010 – Database Attach method


Welcome back to the article in this series on upgrading a SharePoint 2007 content database to SharePoint 2010. Today we will complete our upgrade journey utilising one of the 3 upgrade models that are available to you by Microsoft.  These are listed as follows;
  1. In-place upgrade
  2. Database attach upgrade to a new farm
  3. Hybrid approach (Read –only databases or Detach databases)
There is a wealth of information regarding these different approaches on the Microsoft TechNet site under theUpgrade and Migration Resource Center for SharePoint 2010. I will also outline other resources at the end of this article for convenience.
The upgrade model that I have chosen in this article series is the Database attach upgrade approach in which I will outline in this step by step guide.  The upgrade choice you choose is dependent on a number of factors such as how much down time can you afford and whether you are moving onto newer hardware.  All three options have their strong and weak points which is outlined in the following TechNet article; Determine Upgrade approach (SharePoint 2010)
This article is assuming that your SharePoint 2010 environment is up and running (albeit in beta form).  I have published a 3 part series in getting your SharePoint 2010 environment up and running that you can access from the following links;
  1. Installing SharePoint 2010 Beta on a Windows 2008 R2 Server
  2. Configuring SharePoint 2010 (Beta) Service Applications and User Profile Service Synchronization
  3. Creating your first SharePoint 2010 Beta Web Application and Site Collection
When using the database attach method to upgrade your databases to SharePoint 2010, you need to be aware that none of your configuration settings in SharePoint 2007 will migrate.  You will need to ensure that you have replicated your 2007 environment in the newly created 2010 farm.  Some of the items to consider include the following;
  • Outgoing email server
  • Alternate Access Mappings (AAM)
  • Quota templates
  • Included paths
  • Install any custom or 3rd party features, including web parts, solutions
  • Custom site definitions
  • Custom CSS
In order for you to perform a database attach upgrade into your SharePoint 2010 environment you need to ensure that you have created a new web application.  If you have not done so, you can follow my step by step guide on Creating your first SharePoint 2010 Beta Web Application and Site Collection.
Step 1 :: Restoring a copy of your SharePoint 2007 content database
Now that we have ensured that all our configuration settings are in place, and that all custom features, web parts and solutions have been re-instated, we can now proceed with our upgrade.  You will need to firstly backup and take a copy of your SharePoint 2007 content database and restore it to the newly created SharePoint 2010 farm.
I’m performing my database restore utilising SQL 2008 Management Console.  Right click on Databases and select Restore Database.
Select your source and destination as follows;
image thumb11 Upgrading your Content Database to SharePoint 2010   Database Attach method
Click on Options and ensure you have selected Overwrite the existing database.
image thumb12 Upgrading your Content Database to SharePoint 2010   Database Attach method
Click OK.
We should receive the following confirmation message once the database has been successfully restored.
image thumb13 Upgrading your Content Database to SharePoint 2010   Database Attach method
Step 2 :: Verifying the Content Database
As you have already noticed from our first article, in particular with the introduction of the preupgrade check tool, Microsoft have done a great job in providing us with the necessary tools to ensure a successful upgrade.  The next tool that we will be using is the Test-SPContentDatabase Windows PowerShell cmdlet.  This cmdlet will test and verify that any custom components that are required for this content database has been installed and configured in the SharePoint 2010 environment.
Test-SPContentDatabase –Name <database name> -WebApplication <URL>
Launch the SharePoint 2010 Management Shell and type the above command, ensuring you have entered your Database Name and URL. e.g. below
Test-SPContentDatabase –Name WSS_Content_Intranet -WebApplication http://intranet.georgekhalil.com
The Test-SPContentDatabase is a great reporting tool that will list any missing setup files, web parts and provide you with information on how to remedy any errors.  It will also specify whether these missing features will block the upgrade from succeeding.
image thumb14 Upgrading your Content Database to SharePoint 2010   Database Attach method
You can either attend to these missing features pre or post-upgrade but this depends on whether there are any items that will block the upgrade from proceeding.  Once you have remedied the above, we can proceed with our next tool, which will add the content database to our Web Application.  The stsadm  addcontenddb command line parameter is as follows;
stsadm -o addcontentdb -url <URL> -databasename <database name>
Before proceeding, ensure that there are currently no databases connected to the web application that we will be attaching to.  You can check this via Central Administration / Application Management / Manage content databases.
image thumb15 Upgrading your Content Database to SharePoint 2010   Database Attach method
If one is listed, you can remove the existing attached database by clicking on the actual database name and then clicking on the “Remove content database” check box.
image thumb16 Upgrading your Content Database to SharePoint 2010   Database Attach method
You will receive the above warning which is safe to ignore.  In this instance we are not deleting the actual database but disassociating it from the selected Web Application.  This is the exact same behaviour that was available to us in SharePoint 2007.
We can now proceed and attach our restored SharePoint 2007 database via the following stsadm command line;
stsadm -o addcontentdb -url <URL> -databasename <database name>
In my instance, the command looked as follows;
stsadm -o addcontentdb -url http://intranet.georgekhalil.com -databasename WSS_Content_Intranet
This will initiate the upgrade process as per the below screen capture.
image thumb17 Upgrading your Content Database to SharePoint 2010   Database Attach method
You will eventually receive a message similar to the below advising that the upgrade was completed albeit with errors in my case.  You should review the upgrade log file which is quite extensive and lengthy, and sure enough the errors were all related to missing features etc which I was already aware of.
image thumb18 Upgrading your Content Database to SharePoint 2010   Database Attach method
We can now verify that the upgrade was completed successfully by first navigating back to Central Administration / Application Management / Manage content databases, which now displays the upgraded database under my designated Web Application.
image thumb19 Upgrading your Content Database to SharePoint 2010   Database Attach method
We can also view the upgrade status page which is located within Central Administration / Upgrade and Migration / Check upgrade status.  The page will list all previous upgrade attempts and summarise the number of errors and warnings that may have been encountered.  In my case, there were a number of features that were not installed in the new SharePoint 2010 farm that the current portal relies on.  All of the upgrade logs are located in the following location, providing you with finer detail on the errors and warnings encountered;
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS
image thumb20 Upgrading your Content Database to SharePoint 2010   Database Attach method
By default, your site will retain it’s 2007 theme which Microsoft have done on purpose and you will need to manually change this 2010 if you wish to do so.  This is referred to as the “Visual Upgrade”, providing site administrators the ability to switch to the new look and feel at their own leisure.  This is a great move by the SharePoint product team as the new interface can be quite overwhelming to begin with.  Think about the move from Office 2003-2007 with the introduction of the new ribbon interface.   There was a week or two of frustration for most users before eventually getting the hang of it and finding the new interface to be more productive.
The below screen capture is my upgraded SharePoint 2010 portal running in “SharePoint 2007 theme mode”.
Capture12007 thumb Upgrading your Content Database to SharePoint 2010   Database Attach method
To perform the Visual upgrade, navigate to Site Actions / Visual Upgrade.
Capture12007a thumb Upgrading your Content Database to SharePoint 2010   Database Attach method

Here you are provided with 3 options in which I will select “Use the new SharePoint user interface, and don’t ask me again”.  After clicking on OK, I am now presented with the same site utilising the default SharePoint 2010 theme.
Capture12010 thumb Upgrading your Content Database to SharePoint 2010   Database Attach method
We have now successfully upgraded one of our SharePoint 2010 content databases housing our main Intranet portal, albeit with some missing web parts and features.  So what’s next on the agenda?  Upgrading My Sites of course!  This will involve attaching and upgrading your Shared Service Provider (SSP) to upgrade your user profile information followed by upgrading the My Sites content database.  This process will be left for a future post.
I hope you have found this 2 part series useful and I am interested hear how many of you have attempted a SharePoint 2010 upgrade and your experiences.

Thursday, September 23, 2010

A Visual Studio 2010 Beta Console Application issue in SharePoint 2010 custom code

If you create a console application in Visual Studio 2010 and try to use types such as SPSite from the SharePoint server object model (Microsoft.SharePoint.dll assembly), when you compile your project, you'll get the following error:




You won't get this error if you're using types such as Site from the SharePoint client object model (Microsoft.SharePoint.Client.dll assembly) in your console application.

As you can see from the previous snapshot, Visual Studio 2010 complains that it couldn't find the Web application even though the Web application exists in reality. This happens because of two reasons. First, the active solution platform by default is set to x86:



You need to change that to x64. Pretty easy to do this. Just select New from the drop down menu:


This launches the New Solution Platform dialog. Select x64 and click OK.


After you did that you should see that the right active solution platform shows up:


Second, Visual Studio 2010 by default uses the .NET Framework 4.0. You need to change that to .NET Framework 3.5. To do that, right click the project node in the solution explorer window and select Properties. You should see a drop down menu there for the target framework. Select .NET Framework 3.5 from that menu and save your changes.

Happy Coding!

Wednesday, September 22, 2010

Jquery Library for sharepoint web services

http://spservices.codeplex.com/

Sharepoint WebPart Lifecycle Events

This post describes the lifecycle events of a Sharepoint Connectable WebPart wih a single ViewState backed property

  1. On Page Load
  2. Constructor
  3. OnInit
  4. OnLoad
  5. ConnectionConsumer method is called if web part is connectable (sets the connection providers interface in the webpart)
  6. CreateChildControls
  7. OnPreRender (if your web part is connectable you would typically call the connection provider here to retrieve data)
  8. SaveViewState
  9. Render
  10. RenderChildren
  11. RenderContents
On 1st Postback(PostBack click handler sets ViewState via public Property)

  1. Constructor
  2. OnInit
  3. CreateChildControls
  4. OnLoad
  5. PostBack click handling
  6. ConnectionConsumer method is called if web part is connectable (sets the connection providers interface in the webpart)
  7. OnPreRender (if your web part is connectable you would typically call the connection provider here to retrieve data)
  8. SaveViewState
  9. Render
  10. RenderChildren
  11. RenderContents

On 2nd Postback(PostBack click handler sets ViewState via public Property)



  1. Constructor
  2. OnInit
  3. LoadViewState
  4. CreateChildControls
  5. OnLoad
  6. PostBack click handling
  7. ConnectionConsumer method is called if web part is connectable (sets the connection providers interface in the webpart)
  8. OnPreRender (if your web part is connectable you would typically call the connection provider here to retrieve data)
  9. SaveViewState
  10. Render
  11. RenderChildren
  12. RenderContents

Note that during the 2nd postback, LoadViewState, is called, since in the 1st postback the click handler sets the value of the ViewState backed public property.

Friday, September 17, 2010

Deploy WSP file in SharePoint 2010


  1. Place your .WSP file to the location or any other location
  2. c:\wsp\”your WSP files”
  3. Go to Run command- and set the below path.
  4. C :> CD C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
  5.  This is place u have to ass your solutions file.
  6. Now the prompt look like this
  7. C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN>
  8. Run the below command: It adds the solution to SharePoint Farm Solution.
  9. C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN>stsadm -o addsolution -filename c:\wsp\SmartTools.Charts.wsp
  10. Operation completed successfully.
  11. If u wants to deploy the solution through Command use this command.
  12. stsadm -o deploysolution -name Mysolution.wsp -local -allowGacDeployment -force -url http://Server:3333/
  13. Go to top level site->Site Action –Site Setting-site collection administrator activate the feature over there and add your web part in page

Tuesday, September 14, 2010

Configuring Enterprise Search in SharePoint 2010

We all have to agree that search plays an integral part of any successful SharePoint deployment and is an area that Microsoft continues to invest in with each new release of SharePoint. Microsoft went as far as acquiring FAST 2 years ago which it now offers as a separate add-on to SharePoint for those willing to invest in high end enterprise search. In addition to FAST, SharePoint 2010 search comes in a number of flavors each offering their own feature set and capabilities which I have duplicated at the end of this article as an Appendix for convenience.

Today we will introduce SharePoint Server 2010 Search and eventually work our way up to Microsoft’s latest and greatest FAST Search Server in a near future article. Before we deep dive into the step by step guide I will begin by listing some of the new features that you will come to expect from SharePoint Server 2010 Search. These are as follows;

  • Boolean query syntax has finally been introduced. These include AND, OR and NOT operators in your search queries.
  • Suggestions whilst typing and after running search queries, a feature that we have come to love with major search engines such as Google and Bing.
  • Integrating SharePoint enterprise search with Windows 7, allowing end users to utilise the Windows 7 search box to locate SharePoint 2010 content.
  • Results display has been refined to provide filters for search results such as document type, categories and managed properties.
  • View in Browser capabilities, allows end users to view documents within their own browser utilising Office Web Apps and not having to rely on launching the necessary Microsoft Office Application, or even the need of having it installed on their local machine. This is handy when browsing your SharePoint site via Kiosks and Internet Cafes that may not be running the Microsoft Office Suite.
  • Last but not least, there have been a number of improvements to People Search, including phonetic name and nickname matching, and improved relevance and self search.

Now that we have a taste for what’s to come, let’s begin our configuration.

SharePoint Server Search is a service application which we have come to learn about over the past few articles that it is independent of other services and is no longer tied to the Shared Services Provider (SSP) that was introduced in SharePoint 2007.

SharePoint 2010 search architecture is made up of the Crawler, Indexing Engine, Query Engine and the User Interface and Query Object Model. We now have greater flexibility and expandability with our search design in 2010 and can setup not only multiple Query Servers but can now scale out our Index server and add multiple instances.

Below is a logical overview of the components that will make up our SharePoint 2010 search configuration.

image thumb20 Configuring Enterprise Search in SharePoint 2010

Configuring the Service Application

As always we begin our journey in Central Administration / Application Management / Manage Service Applications.

Click New / Search Service Application.

Name: Enter a name for your Service Application.

FAST Service Application: Select “None” (we will leave the configuration of FAST for a future article)image thumb21 Configuring Enterprise Search in SharePoint 2010

Search Service Account: Click on Register new managed account and ensure your domain account has already been provisioned in Active Directory. I have created a separate search account; e.g. DOMAIN\sp_search

image thumb22 Configuring Enterprise Search in SharePoint 2010

Application Pool for Search Admin Web Service: Create a new application pool for your search admin web service application.

image thumb23 Configuring Enterprise Search in SharePoint 2010

Application Pool for Search Query and Site Settings Web Service: Create a new application pool for your search query web service application.

image thumb24 Configuring Enterprise Search in SharePoint 2010

Click Create

The search service application will begin its configuration process.

image thumb25 Configuring Enterprise Search in SharePoint 2010

You will eventually be presented with confirmation that the search service application was created successfully.

If we now navigate back to Application Management / Manage Service Applications, you will notice that 2 additional services have been added to our list. These are;

  1. Search Service Application (Typical Search Administration page which is similar to that in SharePoint 2007. From here we can create content crawl rules, reset indexes, setup content sources etc).
  2. WSS_UsageApplication (This is a new service in SharePoint 2010 that specifically handles our Usage and Health Data Collection Service Application. This service application handles web analytics such as usage, search query usage, rating usage etc More on this in a future article).

Let’s now launch the Search Administration page by clicking on our Search Service Application.

image thumb26 Configuring Enterprise Search in SharePoint 2010

Our Default content access account should be set to the account that we had specified at the time of provisioning the Search Service Application; i.e. DOMAIN\sp_search

Confirming Permissions

There are a couple of areas to note that we should check to ensure that our Default content access acount (sp_search) has been provided with the appropriate access permissions. Let’s first begin by checking our User Profile Service Application by Navigating to Service Applications / User Profiles. Just highlight the User Profiles and select Administrators from the ribbon.

image thumb37 Configuring Enterprise Search in SharePoint 2010

Our newly provisioned sp_search account should have “Retrieve People Data for Search Crawlers” selected as a permission.

image thumb38 Configuring Enterprise Search in SharePoint 2010

We will also confirm that our sp_search account has the necessary “Read” permissions against the Web Applications being crawled.

Navigate to Central Administration / Application Management / Manage Web Applications. Again, highlight the Web Application in question and from the ribbon select User Policy.

image thumb39 Configuring Enterprise Search in SharePoint 2010

Ensure that the Search Crawling Account is set to the sp_search domain account.

image thumb40 Configuring Enterprise Search in SharePoint 2010

Content Sources

Let’s venture into our content sources listed in the Quick Launch navigation bar under Crawling.

As was the case with SharePoint 2007, our Local SharePoint sites will be detected by default, albeit without a crawl schedule.

image thumb27 Configuring Enterprise Search in SharePoint 2010

Check to see that your Start Addresses are located within your content source via editing the content source from the drop down menu. These includes all SharePoint Web Applications and the sps3 “User Profiles” address.

image thumb28 Configuring Enterprise Search in SharePoint 2010

You can easily create your crawl schedule by clicking on Local SharePoint sites and scrolling down to Crawl Schedules.

image thumb29 Configuring Enterprise Search in SharePoint 2010

Let’s initiate a Full Crawl by clicking on Start all Crawls from the Manage Content Sources page.

Once your crawl has completed, you should confirm that there were no errors encountered during the initial crawl. Usually any errors noted are most likely due to incorrect permission assignments.

Creating a “Basic Search Center” Site

If you haven’t done so already, from your top level site, click on Site Actions / New Site.

Select “Basic Search Center”

image thumb30 Configuring Enterprise Search in SharePoint 2010

Enter a Name and URL and click on Create.

This will provision the Search Center similar to the below.

image thumb31 Configuring Enterprise Search in SharePoint 2010

Creating an “Enterprise Search Center” Site

Let’s also create an Enterprise Search Center for comparison. The key difference here is that we are provided with two tabs for searching, one for Sites and the other for People. The “Enterprise Search Center” will be the search site of choice for most organizations running SharePoint Server.

From Central Administration / Application Management / Site Collections, click on Create site collections. Ensure you are creating the Site Collection below the relevant Web Application.

Enter your Title, Description etc and select the Enterprise Tab under Template selection. Select the Enterprise Search Center, specify your site collection administrators and click OK.

image thumb32 Configuring Enterprise Search in SharePoint 2010

This will provision the Enterprise Search Center similar to the below.

image thumb33 Configuring Enterprise Search in SharePoint 2010

As we have already completed an initial Full crawl earlier, I can now test my new search centers by performing a couple of searches.

Searching Content

image thumb34 Configuring Enterprise Search in SharePoint 2010

Searching People

image thumb35 Configuring Enterprise Search in SharePoint 2010

Now I ran into an issue when trying to search for content located in My Sites. The crawl log displayed the following warning;

“This item and all items under it will not be crawled because the owner has set the NoCrawl flag to prevent it from being searchable”

In order to fix this issue (and this is true for any Site Collection), is to navigate to your My Site host and click on Site Actions / Site Settings.

Click on “Search and offline availability” under Site Administration, and ensure that you have Indexing Site Content, Allow this site to appear in search results? set to “Yes”.

image thumb36 Configuring Enterprise Search in SharePoint 2010

After enabling the indexing of My Sites, I was able to successfully perform My Site Content searches and the warning disappeared from the Crawl Log.

That’s all that is to it in setting up a search center in its most basic form. From here you can expand your service applications over multiple servers providing you with redundancy, scalability and increased performance . Until next time, happy searching :)

References:

TechNet :: Getting Started with Enterprise Search in SharePoint 2010 Products

Appendix

SharePoint Versions Search Comparison

FeatureSharePoint Foundation 2010Search Server 2010 ExpressSearch Server 2010SharePoint Server 2010FAST Search Server 2010 for SharePoint
Basic site searchYYYYY
Best BetsYYYY
Visual Best BetsY
Similar ResultsY
Duplicate ResultsY
Search ScopesYYYY
Search Enhancement based on user contextY
Crawled and Managed PropertiesYYYY*
Query FederationYYYY
Query SuggestionsYYYY
Sort Results on Managed Properties or Rank ProfilesY
Relevancy Tuning by Document or Site PromotionsYYYY*
Shallow Results RefinementYYYY
Deep Results RefinementY
Document PreviewY
Windows 7 FederationYYYY
People SearchYY
Social SearchYY
Taxonomy IntegrationYY
Multi-Tenant HostingYY
Rich Web Indexing SupportY

Thursday, September 2, 2010

Few Best SharePoint blogs

1) Microsoft Sharepoint Team Blog
The official blog of the Microsoft SharePoint Product Group. You can find latest information about sharepoint technology on this blog.
http://blogs.msdn.com/sharepoint/default.aspx

2) To the Sharepoint
The Sharepoint IT Pro documentation team blog. We're the Microsoft SharePoint IT Pro documentation team. We're passionate about providing the right documentation for any IT Pro implementing, managing, or supporting SharePoint in their environment. We'd love to hear your suggestions about ways we can improve content for you.
http://blogs.technet.com/tothesharepoint/

3) Arpan Shah – Sharepoint Blog
I'm a Director at Microsoft Corporation (Redmond, WA) who owns Technical Product Management for SharePoint Products and Technologies. While I sometimes post personal comments, this blog's primary purpose is to provide information on SharePoint technology along with Collaboration, ECM and Search industry trends. You can also follow me on twitter @arpanshah.
http://blogs.msdn.com/arpans/about.aspx

4) Sharepoint Joel
Joel is a senior product manager and SharePoint evangelist at Quest, where he is responsible for product direction and strategy. He is well known in the SharePoint community as an enthusiastic trainer, evangelist and architect, and he maintains a popular blog. Joel is a frequent speaker at popular technical conferences, such as Microsoft TechEd, and often presents to local SharePoint user groups. Prior to Quest, Joel worked at Microsoft and was involved in the first Microsoft global deployment of SharePoint. During his Microsoft tenure, Joel helped various customers achieve the critical governance they needed to upgrade and achieve scale with SharePoint 2007. He later designed the extranet and hosted SharePoint deployments.
http://www.sharepointjoel.com/default.aspx

5) Harbar.net
Spencer Harbar is an enterprise architect who helps organizations implement and drive value from solutions based upon Microsoft SharePoint. With over fifteen years of commercial experience in the architecture, design, development, deployment and operational service management of Web based applications and hosting platforms, his broad base of fundamental skills routinely enables Europe’s largest organizations to succeed with SharePoint.
http://harbar.net/Default.aspx

6) Andrew Connell- Sharepoint MVP Blog
I am a Microsoft developer specializing in the .NET Framework and the Office Server System, specifically Microsoft Content Management Server 2002 and Windows SharePoint Services / SharePoint Portal Server 2003. In April of 2005 & 2006 I was recognized by Microsoft for my community contributions by being awarded Most Valuable Professional for Microsoft Content Management Server.
http://www.andrewconnell.com/blog/

7) Sharepoint Tricks
Sharepoint Tips And Tricks is Ishai Sagi's sharepoint information blog. It specializes in Microsoft SharePoint technologies, including web parts, development, configuration, customization, and best practices for the use of Microsoft SharePoint Server and Windows SharePoint Services. It also provides some related Office Information, including VSTO and VSTA and other office application development tips.
http://www.sharepoint-tips.com/

8) Liam Cleary – Sharepoint MVP Blog
All about the Strategy, Design, Customisation, Deployment and Development of SharePoint and its related Technologies
http://www.helloitsliam.com/default.aspx

9) Sharepoint Solutions Team Blog
Since 2004, a blog by members of the SharePoint Solutions team - experts and pioneers on Microsoft SharePoint. SharePoint training is at the heart of all we do. For many organizations, the best place to start is in one of our public or on-site custom-created and expert-led SharePoint training classes. We have been recognized as a pioneer in the field of SharePoint training since Microsoft introduced SharePoint 2003.
http://sharepointsolutions.blogspot.com/

10) SharePoint Automation
Automating SharePoint 2007 Configurations via STSADM and PowerShell. Gary Lapointe is a two-time MOSS MVP specializing in deployment and development.
http://stsadm.blogspot.com/


Besides this Other Interesting Sharepoint Blogs
http://sharepoint.mindsharpblogs.com/default.aspx
http://blogs.microlinkllc.com/tresing/default.aspx

http://sharepointsolutions.blogspot.com
http://furuknap.blogspot.com
http://www.Sharepoint-Blogs.com
http://miss-sharepoint.blogspot.com
http://manish-sharepoint.blogspot.com
http://dotnetguts.blogspot.com
http://www.sharepointfeeds.com
http://jopx.blogspot.com
http://www.fivenumber.com/

SharePoint 2010 Developer Exam-70-573


MCTS SharePoint 2010 Application Development 70-573 Study Guide

I recently sat and passed the MCTS SharePoint 2010 Application Development 70-573 exam. I thought I’d share the list of resources that helped me with my revision.
There are several study guides about now for example: http://blog.beckybertram.com/Lists/Exam%2070573%20Study%20Guide/AllItems.aspxand http://techtrainingnotes.blogspot.com/2010/05/sharepoint-2010-part-1-preparing-for-70.html, but I wanted to record the articles and blogs etc I’d used.
To help I’ve copied in the Microsoft learning content from http://www.microsoft.com/learning/en/us/exam.aspx?ID=70-573&locale=en-us#tab2 
Working with the SharePoint User Interface (19%)
Developing Web Parts and Controls (21%)
Developing Business Logic (19%)
Working With SharePoint Data (22%)
Stabilizing and Deploying SharePoint Components (19%)