And  if you are able to debug the same page in Visual Studio 2012 using the latest versions of any of the following browsers without any issues:

• Opera,
• Chrome,
• Firefox and
• Safari etc.

Then make sure that Compatibility View settings in IE 10 are turned “Off” for the domain (or host name) of the IIS site where your page is hosted. In my case I found that “localhost” was added to Compatibility View, so just removing it from there solved the problem.

For more details on why this is an issue, will recommend reading following MSDN article:

Defining Document Compatibility

 Update 18-Aug-2013: Changed the blog title to reflect that this applies only to JQuery 2.x. ['JSON' is undefined] is not an issue with JQuery 1.x. 

Following tables further detail out IE 10 behaviour across compatibility modes, settings and jQuery versions:

1.  First get a reference to your web application, using following command

$webApp = Get-SPWebApplication – Identity <URL of your web application>

2.  Get the list of zones present in the web application, using following command

$webApp.IisSettings.Keys

Previous command should have shown you names of all the zones in your web application, in our case we saw only one zone called “Default”.

If you investigate the members of “$webApp.IisSettings("Default")”, you will see following

3.  In this case I had to enable Kerberos on this web application, so will use following commands:

$webApp.IisSettings.Item("Default").DisableKerberos = $false

$webApp.Update()

That’s it and you are done changing IIS authentication settings for the web application! 

1. Site column when added to a list or library should not be editable through UI (even datasheet view)
2. Users should be able to add list columns based on site column to personal or shared list views of that list
3. Users should not be able to modify any settings of the list column based on this site column (depends on field type and priviliges).
4. Any updates to list column values can only be done programmatically

Long story short, I noticed that InfoPath promoted properties which are not editable have all these characteristics. So, I created site column defintion similar to one that is generated automatically for site columns based on an InfoPath form's readonly promoted property.

Here is a sample readonly site column definition:

<Field ID="{102ED08D-CE13-4f56-B07E-7B5118191949}" Type="Text" Name="ReadonlyTest1" DisplayName="Read Only Test 1" StaticName="ReadonlyTest1" Group="Test Columns" Hidden="FALSE" ReadOnly="TRUE" Required="FALSE" ShowInDisplayForm="TRUE" ShowInViewForms="TRUE" PITarget="" PrimaryPITarget="" PIAttribute="" PrimaryPIAttribute="" Node=""/>

Essentially, add these attributes to any site column definition to make it readonly:

Hidden="FALSE" ReadOnly="TRUE" Required="FALSE" PITarget="" PrimaryPITarget="" PIAttribute="" PrimaryPIAttribute="" Node=""

Following is a sample code to modify the value of list column based on above sample site column when it's added to a custom list called "Test":

using (SPSite site = new SPSite("https://<your site>/"))

using (SPWeb web = site.RootWeb)

{

SPList oList = web.Lists["Test"];

SPListItem oListItem = oList.Items[0];

oListItem["Read Only Test 1"] = "Updated Text";

oListItem.Update();

}

In this blog entry we will show how to create a SharePoint site such that anonymous users should be able to contribute content into lists/libraries and also browse the site.

To do so follow the steps shown below:

Step 1. Create a new or extend an existing web application with settings:

Central Administration > Application Management > Create or Extend Web Application > Create New Web Application> Security Configuration > Allow Anonymous = Yes

Figure 1 – New Web Application Security Configuration

You can also edit this setting for an existing web application through:

Central Administration > Application Management > Authentication Providers > Edit Authentication > Anonymous Access > Enable anonymous access = True

Figure 2 - Existing Web Application Security Configuration

Step 2. Create your site collection in the web application that was created or modified in Step 1.

Step 3. Enable the anonymous access to this site collection, go to

Site Settings > Advanced permissions (https://<your site collection>/_layouts/user.aspx)

Click on Settings > Anonymous Access

Figure 3 - Site Collection Anonymous Access

And then enable anonymous access for site collection:

Anonymous Access > Anonymous users can access = Entire Web Site

Figure 4 - Enable Anonymous Access for Web Site

Step 4. Enable the anonymous access on lists and document libraries that you want anonymous users to view, edit etc.

Following is an excerpt from TechNet article that can be found here:

1. Go to the home page of your Web site and, in the left navigation pane, click View All Site Content.

2. Click the list on which you want to enable anonymous access.

3. On the Settings menu, click List Settings.

4. On the Customize List page, in the Permissions and Management section, click Permissions for this list.

5. On the Permissions page, on the Actions menu, click Edit Permissions. A dialog box is displayed informing you that you are about to create unique permissions for this list. Click OK.

Figure 5 - Edit List / Document Library Permissions

6. On the Settings menu, click Anonymous Access.

Figure 6 - List/Library Anonymous Access

Select permissions for users who have anonymous access to the list, and then click OK.

Figure 7 - List/Library Anonymous Access Permissions

In case of InfoPath 2007 browser enabled forms, there is a very handy ActiveX control available OOB, to find more about it, read following article from InfoPath Team :

Using the Contact Selector Control

Now, just in case like me, if you find above control inept in certain scenarios where you wish to make sure that only single contact is selected by end user from AD or User Profile.

And, if you find writing code for custom UI that fetches and displays users from AD or User Profiles in SharePoint Server, is too much a task and you need some sort of workaround for this issue and still be able to use the contact selector control. Then, try adding following code to Contact Selector control's (named gpContactSelector here) Changed Event:

public void gpContactSelector_Changed(object sender, XmlEventArgs e)
{
  string senderLocalName = ((XPathNavigator)sender).LocalName;

  if ( senderLocalName == "DisplayName")
  {
      XPathNavigator navigator = MainDataSource.CreateNavigator().SelectSingleNode("/my:myFields/my:gpContactSelector", NamespaceManager);
      if (navigator != null)
      {
          int count = navigator.SelectChildren(XPathNodeType.Element).Count;
          if (count > 1)
          {
              this.Errors.Add(navigator, "InvalidUserCount", "Can't select multiple users.");
          }
      }
  }
  else if (senderLocalName == "Person")
  {
      XPathNavigator navigator = MainDataSource.CreateNavigator().SelectSingleNode("/my:myFields/my:gpContactSelector", NamespaceManager);
      if (navigator != null)
      {
          int count = navigator.SelectChildren(XPathNodeType.Element).Count;
          if (count == 1)
          {
              if (Errors.Count >= 1)
              {
                  try
                  {
                      this.Errors.Delete("InvalidUserCount");
                  }
                  catch (ArgumentException)
                  {
                       // Do nothing
                  }
                  catch (Exception)
                  {
                      throw;
                  }
              }
          }
      }
  }
}

The code snippet shown above will add an error object in form's error collection whenever an end user selects more than one contact. This should make sure that user is not allowed to submit the form, unless, the error is resolved by end user manually, i.e. by removing all the selected contacts save one from the Contact Selector control in the UI. 

We can also automate this removal of extra contacts in code behind, and then warn end users by adding an error object in the forms error collection or by displaying a message in UI.

However, do make sure that your customer is aware of this scenario and is okay with this. Otherwise, you may find a bunch of confused end users, trying to figure out, what is happening to all those contacts they selected.

Catch in this approach is, end users are not warned until they have selected a bunch of contacts. If this becomes a major usability issue and your customer is not ready to buy in, then, IMHO only choice is creating a custom UI for contact selection.