Let me introduce a great company GoodPoint Software, focused on Developing SharePoint Apps for SharePoint Store.
The Company goals are pretty ambitious, for example, by the end of 2015 it is planned to be the biggest SharePoint Store Apps Publisher. And I'm confident they'll succeed, they already have a big bunch of SharePoint Apps completed.

Error "This functionality is unavailable for fields not associated with a list" at SPField.Update()

Symptoms:

Sometimes it is necessary to modify your content type's property in a list without affecting to list items data.
The easiest way to do it is PowerShell:

$web = Get-SPWeb http://web-url
$list = $web.Lists["listName"]
$list.ContentTypes["CTName"].Fields["fieldName"].someProperty = someValue
$list.ContentTypes["CTName"].Fields["fieldName"].Update()
Oops. Error: “This functionality is unavailable for fields not associated with a list”

The reason:

SPField which is going to be modified belongs to Site Columns (SPWeb.Fields collection). Editing this SPField is unavailable.
SiteColumns are stored inside ContentTypes as FieldLinks, not as Fields.

The solution:

Use SPContentType.FieldLinks instead of SPContentType.Fields collection.
$web = Get-SPWeb http://web-url
$list = $web.Lists["listName"]
$list.ContentTypes["CTName"].FieldLinks["fieldName"].someProperty = someValue
$list.ContentTypes["CTName"].Update()
$web.Dispose()
Successfully completed without errors.

Disable all event receivers from non-receiver code

There is a nice pattern for temporary disabling all receivers from code:
You can find it here.

I recommend using it.

Windows Server 2012 is not supported by SharePoint 2010 until SharePoint SP2

Today I was really surprised.
SharePoint 2010 cannot be installed on Windows Server 2012 operating system.
The situation will be fixed only after releasing SharePoint 2010 Service Pack 2 which is even not announced yet.

Here is Microsoft KB article about it.

Hope SP2 will be released soon.


Update1:  It's funny but SharePoint 2010 is also cannot be installed on machines with Office 2013.

SharePoint 2013 Request Management Service. Lack of UI for configuring.

This week I studied at SharePoint 2013 Ignite ITPRO training in Moscow.
I learned very nice SharePoint 2013 functionality called "Request Management".

You can get a lot of info about RM here and here.

However I found that there is NO User Interface at SP2013 for Configuring Request Management Service. It should be configured using PowerShell only. That's nice for crazy geek admins, but not for me:)

I think one can create UI for RM and sell it. It would be awesome to sell it using new Office Store. But unfortunately new App Model doesn't support this task. We can use S2S for impersonating, but the new Client Object Model doesn't have any methods for configuring farm services such as Remote Management Service.
So the task of creating UI for SharePoint 2013 Request Management can only be done using classical SP2010 approach e.g. create non App-based solution with Server-side SharePoint Object Model.

Well, maybe I will try to do it in the future.

Visual Studio 2012 Bug in Visual List Designer (ArgumentException: Requested value 'People Only' was not found.)

Today I'm creating some list definitions in Visual Studio 2012.
I work with UserFields and I set it's properties: