Skip to main content

What is SPObject.Resolve()

This is my professional blog where I will post things, thoughts and ideas that I face in my daily work as a developer. And because I’m a SharePoint developer most of the topics here will be about SharePoint 2010 and integration of applications.

In short about me :
   - at this moment I have 3 years of experience as a developer and have worked in the following companies:
        Interconsult Bulgaria
        ( April 2010 to present )
        Vereo
        ( September 2008 to April 2010 )
        Telerik
        ( February 2008 to May 2008 )
        Weblancers
        ( June 2007 to February 2008 )

   - I have developed Windows Froms and ASP .NET applications but my interests and passion are in building SharePoint solutions

   - I have 3 certificates for SharePoint - although I don’t think MS exams are something really important I think a developer who pretend to be a good professional has to take the exams in his area.


Why to have a blog ?

SharePoint is area where is very difficult to write or show something really new. Of course, if you are a MVP or guy from MS SharePoint team you can but in the other cases – it’s really difficult.
Even though having a professional blog is important. This is the stage to show your ideas, problems and thoughts. It’s a test for yourself to understand whether you are able to write interesting and important topics or not and of course, this is a way to build your unofficial CV showing your way of thinking and personal progress. And of course, to make your English and way of writing better.

So ….

    try
    {
          SPObject.Resolve()
    }
    catch(Feedback fd)
    {
           PersonalUpgrade.Load(fd);
    }
    finally
    {
           ShareThoughtsAndIdeasToFindWhereTheRightDirectionIs();
    }


. . .
Labels:

Comments

Post a Comment

Popular posts from this blog

ClientPeoplePicker in SharePoint 2013

Start using SharePoint 2013 I noticed that the way for selecting people or groups is changed. The new way is simple – just ‘Enter name or email address’ without any icons for ‘Check Names’ or ‘Browse’. I guess that the PeoplePicker is changed but NO. PeoplePicker sitll has the same functionality as before. There is a new control called ClientPeoplePicker . How to use it: 1. Add this references <% @ Register TagPrefix ="wssawc" Namespace ="Microsoft.SharePoint.WebControls" Assembly ="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> 2. Add the following control declaration       < wssawc : ClientPeoplePicker          Required ="true"          ValidationEnabled ="true"          ID ="peoplePicker"          runat ="server"   ...
14 comments
Read more

Error: A duplicate field name "xxxx" was found

Soon I have some experience with migrating solution from SharePoint 2010 to SharePoint 2013. The migration was on 3 steps. First one was just to copy the custom fields, content types and list definitions from the old VS 2010 project into a new VS 2012 project for SharePoint 2013. Looks like pretty simple task but ….. The problem:  Error “ A duplicate field name "xxxx" was found ” when the feature for provisioning the fields and content types is activated. The solution: Review the field definitions and make sure no field has Name property equal to some of the ‘reserved’ values. Explanations: In SharePoint 2010 there was no problem to have these fields as a definition of custom fields: < Field     Type = " Note "     ID = " {893FB9BC-2DA4-4451-A1D1-88010CDC6A08} "     Name = " Description "     StaticName = " Description "     DisplayName = " Description 1 "     Requi...
1 comment
Read more

SharePoint and List Joins with CAML

This came to me as an issue when I started migrating one project from SharePoint 2010 to SharePoint 2013. The code uses LINQ to SharePoint and it was not written in a clever way. We decide to use CAML queries and optimize the code. The scenario: Create gridview that gathers information from three(or more) lists. The problem: How to create the CAML query joins and projected fields correctly. Explanation : Option 1: Get generated CAML query from LINQ to SharePoint code This doesn’t work. I wrote the LINQ to SharePoint code connected the three lists. When I executed the code the following error was thrown – “ The query uses unsupported elements, such as references to more than one list, or the projection of a complete entity by using EntityRef/EntitySet. ” Here is some explanation about it and why this can’t be used. Option 2: Write the query yourself I found this article in MSDN . Read it ! The second part in it is exactly my scenario. But it takes me a lot of time to un...
Post a Comment
Read more