SharePoint 4 Developers | Additional reference guide in .NET / SharePoint Development

SharePoint 2010 Certified

13. July 2010 Admin News (0)

Hi folks,

Today I received the outcome of the SharePoint Development BETA exams (71-573 / 71-576) I took last month and for my surprise I succeed them. The tests were the Microsoft SharePoint 2010, Application Development and the Designing and Developing Microsoft SharePoint 2010 Applications. Both of them were tough tests with more than 80 questions, comprising the following technical tasks below:

(71-573) TS: Microsoft SharePoint 2010, Application Development

Working with the SharePoint User Interface
Developing Web Parts and Controls
Developing Business Logic
Working With SharePoint Data
Stabilizing and Deploying SharePoint Components

(71-576) PRO: Designing and Developing Microsoft SharePoint 2010 Applications

Creating an Application Design
Designing UX
Managing Application Development
Optimizing SharePoint Application Design
Designing SharePoint Composite Applications
Designing SharePoint Solutions and Features

From now on these tests are going to have fewer questions, because they have evoluted to a regular exam. The exam numbers have changed to 70-573 and 70-576 as well. If you want to know more about them, get more details in the following links:
http://www.microsoft.com/learning/en/us/exam.aspx?ID=70-573
http://www.microsoft.com/learning/en/us/exam.aspx?ID=70-576

Now I am a SharePoint 2010 Certified! Awesome!

Cheers,

Marcel Medina

Click here to read the same content in Portuguese.

Site Definitions – A legacy

7. July 2010 Admin Tips and Tricks (0)

Share

Hi folks,

In this post I want to talk a little about Site Definitions and the legacy you get when using them.

Site Definitions are present in all SharePoint installations, considering the last recent versions:

WSS 3.0 and MOSS 2007 – available at the directory %\12\TEMPLATE\SiteTemplates
SharePoint Foundation and Server 2010 - available at the directory %\14\TEMPLATE\SiteTemplates

So using these templates for customisation and extension is really normal, right?

That's not quite right…its utilisation at first seems to be the best solution, because it allows us to create definitions of the objects that will compose the Web Site. Besides we can make it available in Tabs at the moment of creating a Web Site, which makes easy for users to select the correct Template.

The main issue is the legacy that this solution gives you. Currently I am working with the Upgrade of SharePoint 2010 Solutions developed for MOSS 2007 and have seen how complex is to upgrade Heavy Site Definitions. First you laugh, then you cry! :)

As a developer I always chase a way to create reusable code, and the utilisation of Site Definitions allows us that. You must know that is more productive the development based on something that already exists rather than creating something from the scratch.

Nevertheless it is important to understand this legacy and its futures consequences. This concern applies to all solutions in any technology! I agree that in most of the cases the SharePoint development comes from experience, because in many cases documentation is scarce.

Best practices are important, in this specific case I give you some tips:

Use Light Site Definitions, that contain few objects (just the essential ones).
After creating a Site Definition, use Feature Stapling to add other objects.
If your solution works without using a Custom Site Definition, probably you don’t need it.

Unlike those that come to abolish such use [nothing against the IT guys :)], I am for it because I have the following thinking: if the technology allows us to use this resource, so it means we can use it. Just be responsible and pay attention to its purpose and the right utilisation.

Be welcome to comment if you wish!

Please find below some links related to this post:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;898631
http://msdn.microsoft.com/en-us/library/aa978512.aspx
http://msdn.microsoft.com/en-us/library/aa979683.aspx
http://msdn.microsoft.com/en-us/library/ms454677.aspx
http://spg.codeplex.com

Cheers,

Marcel Medina

Click here to read the same content in Portuguese.

Error occurred in deployment step 'Add Solution': Failed to load receiver assembly

25. June 2010 Admin Troubleshooting (3)

Share

Hi folks,

The integration Visual Studio 2010 x SharePoint Foundation 2010 when deploying BDC Model Solutions still presents some issues. The problem occurs in Visual Studio because it cannot find the required DLLs to perform the operation. The error messages are listed below:

Problems:

Error occurred in deployment step 'Add Solution': Failed to load receiver assembly "Microsoft.Office.SharePoint.ClientExtensions, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" for feature "<Sua Feature>: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Office.SharePoint.ClientExtensions, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.Office.SharePoint.ClientExtensions, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'
   at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
   at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
   at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
   at System.Reflection.Assembly.Load(String assemblyString)
   at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject()

Error occurred in deployment step 'Add Solution': Could not load file or assembly 'Microsoft.Office.Server, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot find the file specified.