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 )
        ( September 2008 to April 2010 )
        ( February 2008 to May 2008 )
        ( 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 ….

    catch(Feedback fd)

. . .


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=, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> 2. Add the following control declaration       < wssawc : ClientPeoplePicker          Required ="true"          ValidationEnabled ="true"          ID ="peoplePicker"          runat ="server"          InitialHelpText =" <% $Resources:wss,aclinv_PickerIntialHelperText %> "          VisibleSu

Using SharePoint Attachments' controls with elevated security

The scenario:  Create custom forms for Add/Edit/Delete items to a list which is not accessible by the regular users. The forms should support working with attachments. The problem: The default SharePoint controls don’t work if the current user doesn’t have access to the list items. The solution: Use custom code for generating the SharePoint default HTML so the out-of-the-box javascript works correct. Explanations:  The scenario occurs when some list need to be hidden form the users. The list has broken security inheritance and users can't navigate directly to it. Working with its fields requires crating web warts or application pages with appropriate controls on them and server-side code running under elevated privileges. The issue here is that the OOTB (out-of-the-box) controls for Attachments don't work if the user doesn’t have access to the related list item. The OOTB controls are: AttachmentsField , AttachmentUpload , AttachmentButton . There is a lot of code

The column name that you entered is already in use or reserved. Choose another name.

The problem:  You want to create column with a specific name in SharePoint but SharePoint gives you the message "The column name that you entered is already in use or reserved. Choose another name." Why this is a problem? Because you need to create custom columns and content types using the default SharePoint interface. And the business users have to see properly named columns - for example "Description", not "My Description". Solution: It is important to know something technical about SharePoint (versions Office 365, 2013, 2010):  - it supports columns with same Display Names.  - you can’t have columns with same Internal names Let’s implement the following common scenario: You are creating a SharePoint customization and you need the following column:    Type: Multiple lines of text    Internal Name: MyProjectDescription    Display Name: Description  Here is the correct way to achieve it: 1. Create the column MyProjectDescription. T