New version of the BHOLD SP1 was out on Jan 8th and has been published on MSDN and TechNet for download. Interesting suite.

• FIM 2010 R2, http://technet.microsoft.com/en-us/library/hh322910(v=ws.10).aspx
• Microsoft BHOLD Suite, http://technet.microsoft.com/en-us/library/jj134096(v=ws.10).aspx

Microsoft® Forefront Identity Manager (FIM 2010) 2010 enables organizations to manage the entire lifecycle of user identities and their associated credentials. It can be configured to synchronize identities, centrally manage certificates and passwords, and provision users across heterogeneous systems. With FIM 2010, IT organizations can define and automate the processes used to manage identities from creation to retirement.

Microsoft BHOLD Suite extends these capabilities of FIM 2010 by adding role-based access control to FIM 2010, enabling organizations to define user roles and to control access to sensitive data and applications in a way that is appropriate for those roles. BHOLD Suite includes services and tools that simplify the modeling of the role relationships within the organization, map those roles to rights, and to verify that the role definitions and associated rights are correctly applied to users. These capabilities are fully integrated with FIM 2010, providing a seamless experience for end users and IT staff alike.

This guide helps you understand how BHOLD Suite works with FIM 2010 and covers the following topics:

• Role-based access control
• Attestation
• Analytics
• Reporting
• FIM integration
• FIM provisioning

Incoming search terms:

• bhold and sharepoint
• forefront for sharepoint 2013
• forefront protection for sharepoint 2013

What is SharePoint Claims Authentication?

The claims-based identity is an identity model in Microsoft SharePoint Foundation 2010 and SharePoint Server 2010 that includes features such as authentication across users of Windows-based systems and systems that are not Windows-based, multiple authentication types, stronger real-time authentication, a wider set of principal types, and delegation of user identity between applications.

Claims-based identity is based on the user obtaining a security token that is digitally signed by a commonly trusted identity provider and contains a set of claims. Each claim represents a specific item of data about the user such as his or her name, group memberships, and role on the network. Claims-based authentication is user authentication that utilizes claims-based identity technologies and infrastructure. Applications that support claims-based authentication obtain the security token from the user and use the information within the claims to determine access to resources. No separate query to a directory service like Active Directory is needed.

In a simple analogy:

You check in at the Airport (Authentication)
- present credentials (Passport)
- credentials are validated by security guard

You receive a boarding pass (Signed Claims)
- Seat, Frequent Flyer, Gate etc.

Think of a claim as a piece of identity information (for example, name, e-mail address, age, or membership in the Sales role). The more claims your application receives, the more you know about your user. These are called “claims” rather than “attributes,” as is commonly used in describing enterprise directories, because of the delivery method. In this model, your application does not look up user attributes in a directory. Instead, the user delivers claims to your application, and your application examines them. Each claim is made by an issuer, and you trust the claim only as much as you trust the issuer. For example, you trust a claim made by your company’s domain controller more than you trust a claim made by the user.

Claims-based authentication in Windows is built on Windows Identity Foundation (WIF), which was formerly known as the Security Token Service, or STS. Many areas of SharePoint still refer to the name STS so it’s important to understand that it and WIF are one in the same. The Security Token Service comes pre-baked into the standard SharePoint 2010 install:

The Security Token Service Application in Central Administration:

The Security Token Service Application in IIS:




WIF is a set of .NET Framework classes that is used to implement claims-based identity. Claims-based authentication relies on standards such as WS-Federation, WS-Trust, and protocols such as SAML.

Microsoft recommends Claims-based authentication as the preferred provider to use on fresh SharePoint 2010 installs. You can configure this on a per-Web Application basis in SharePoint via the following dialog in Central Admin > Web Applications > Manage Web Applications > Ribbon Bar – New

If you select Classic-Mode Authentication, you configure the Web application to use Windows authentication and the user accounts are treated by SharePoint Server 2010 as Active Directory Domain Services (AD DS) accounts.

If you select Claims-Based Authentication, SharePoint Server 2010 automatically changes all user accounts to claims identities, resulting in a claims token for each user. The claims token contains the claims pertaining to the user. Windows accounts are converted into Windows claims. Forms-based membership users are transformed into forms-based authentication claims. Claims that are included in SAML-based tokens can be used by SharePoint Server 2010. Additionally, SharePoint developers and administrators can augment user tokens with additional claims. For example, Windows user accounts and forms-based accounts can be augmented with additional claims that are used by SharePoint Server 2010.

*Both map authenticated users to the same SPUser object (security principles)

What does Claims look like/feel like?

The core process of Claims is illustrated as follows:

The core currency of Claims is the identity token.

 
EXAMPLE 1:
i:0#.w|contoso\jsmith
EXAMPLE 2:
i:0#.w|jsmith@contoso.com

i = Identity Claim all other claims will use “c” as opposed to “i”
: = Colon separator
0 = Reserved to support future Claims
#/? = Claim Type Encoded Value. The out of the box claim types will have a hardcoded encoded value, this will enable parity across farms.
E.g. Key: ? Value: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier

           Key: # Value: http://schemas.microsoft.com/sharepoint/2009/08/claims/userlogonname

./0 = Claim Value Type. The out of the box claim value types will have a hardcoded encoded value, this will enable parity across farms.

            E.g. Key: . Value: urn:oasis:names:tc:xacml:1.0:data-type:rfc822Name

            Key: 0 Value: http://www.w3.org/2001/XMLSchema#string –

w/m/r/t/p/s = Original Issuer Type -> w = windows, m = membership, r = role, t = trusted STS, p = personal card, s= local sts claim

Why do I want to use Claims?

1. Decouples Authentication logic from Authorization and Personalization logic – this means speed and flexibility
2. Provides a common way for applications to acquire the identity information the need about users
3. Cloud-ready – lays the foundation to be able to Authenticate against Azure, Facebook, Google, Windows Live ID etc.
4. Federation – Partner networks, business to business, subsidiaries can all interact in the same sphere of authentication, cross machine and cross-farm
5. Supports existing identity infrastructure (Active Directory, LDAP, SQL, WebSSO etc.)
6. Standards-based and interoperable

Bonus Prize:
7. In SP 2010 we can have a single Web Application configured to use multiple authentication types which allows different auth types to be served from one URL:

Claims Gotchas

General issues for all Claims implementations
- Search crawler requires NTLM in the zone it uses
- Office Client Integration (2007 SP2+, 2010 are minimum requirements in order to maintain Client integration e.g. fluid editing of Word Document)
- SharePoint Designer does not support working with Claims Enabled Endpoints for Web Services

Migration issues when moving from Classic to Claims
- When upgrading from Classic to Claims, you will need to migrate users and Test & re-work customizations (Web parts, workflows etc.)
- After you move to Windows claims, you cannot go back to Windows classic. Ensure that you have good backups before you start and try your migration in a lab first before moving into production.
- Existing alerts may not fire, if this occurs the only workaround may be to delete and recreate the alerts
- Search crawl may not function, double-check the web application policies and ensure that the search crawl account shows the new converted account name. If it does not, you must manually create a new policy for the crawl account.

References

Configure Forms-based Authentication for a Claims-based Web Application
Configure the Security Token Service
SharePoint and Claims-based Identity
A Guide to Claims-based Identity and Access Control
SharePoint Server 2010 IT Professional Evaluation Guide
Plan Authentication Methods (SharePoint Server 2010) on TechNet
Claims-Based identity with Windows
Claims to Windows Token Service Overview (MSDN)
Claims Based Authentication in SharePoint 2010
Friends don’t Let Friends Use Claims Based Authentication

Incoming search terms:

• claim based authentication in sharepoint 2010
• claim authentication sharepoint
• sharepoint 2013saml authenticaton sorry no access t
• sharepoint 2010 convert to claims based authentication
• problems with sharepoint 2013 form authentication
• edit user profile sharepoint 2010 claims authentication
• custom windows authentication page sharepoint 2013
• claims based authentication sharepoint
• claims based authentication guide
• claim based authentication sharepoint

What is OneNote?

Has to be asked – a surprising number of people are not aware of what OneNote is for and how powerful it can be for keeping organized.

OneNote is a Digital notebook application that enables users to gather, organize, and search notes and other types of information, and to share those notes with others.

OneNote homepage: http://office.microsoft.com/en-ca/onenote/

What Are OneNote Documents?

Unsurprisingly, OneNote 2010 documents are XML documents not unlike .DOCX or .XLSX files. This means CRUD operations incur less complexity and overhead as they would if they were old school binary documents.

For collaboration, the open XML format that your OneNote “stuff” (including the hierarchy of Section Groups & Sections, text, styling, and embedded images and other media) follows makes it easy to synch across disparate devices such as desktops & mobile devices (non-Windows devices included).

That’s Great Keith, How About A Bunch of Code?

I knew you’d ask! Here you go, this is an update of a OneNote page, at the plumbing level:

static void UpdatePageContent()
    {
        OneNote.Application onApplication = new OneNote.Application();
        String strImportXML;
strImportXML = "<?xml version=\"1.0\"?>" +
            "<one:Page xmlns:one=\"http://schemas.microsoft.com/office/onenote/12/2004/onenote\"
            ID=\"{3428B7BB-EF39-4B9C-A167-3FAE20630C37}{1}{B0}\">" +
            "    <one:PageSettings RTL=\"false\" color=\"automatic\">" +
            "        <one:PageSize>" +
            "            <one:Automatic/>" +
            "        </one:PageSize>" +
            "        <one:RuleLines visible=\"false\"/>" +
            "    </one:PageSettings>" +
            "    <one:Title style=\"font-family:Calibri;
                 font-size:17.0pt\" lang=\"en-US\">" +
            "        <one:OE alignment=\"left\">" +
            "            <one:T>" +
            "                <![CDATA[My Sample Page]]>" +
            "            </one:T>" +
            "        </one:OE>" +
            "    </one:Title>" +
            "    <one:Outline >" +
            "        <one:Position x=\"120\" y=\"160\"/>" +
            "        <one:Size width=\"120\" height=\"15\"/>" +
            "        <one:OEChildren>" +
            "            <one:OE alignment=\"left\">" +
            "                <one:T>" +
            "                    <![CDATA[Sample Text]]>" +
            "                </one:T>" +
            "            </one:OE>" +
            "        </one:OEChildren>" +
            "    </one:Outline>" +
            "</one:Page>";
// Update the page content.
        onApplication.UpdatePageContent(strImportXML, System.DateTime.MinValue);
    }

My Brain Hurts, What Does that Crap Mean?

It means, that since we can see it’s a simple XML (text file) update method, then the access methods for performing these updates are also likely to be simple. That they be. Web Services are a fundamental backbone to the Office suite and SharePoint, and OneNote is no black sheep.

There are three methods used by OneNote for communicating:

HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV):

File Synchronization via SOAP over HTTP Protocol Specification

Windows Live SkyDrive Save to Web SOAP Web Service

All three of these methods are simply communication over HTTP via XML.

What Protocol is Used When?

To transfer and synchronize files that are stored on a server running SharePoint Products and Technologies, OneNote 2013 or OneNote 2010 determine which Web authoring protocol to use by sending a SOAP call to the protocol server by using the File Synchronization via SOAP over HTTP Protocol (MS-FSSHTTP), and then processing the response as follows.

1. If the protocol server responds in the format that is defined by the File Synchronization via SOAP over HTTP Protocol, OneNote 2013 or OneNote 2010 use the File Synchronization via SOAP over HTTP Protocol to access the file.

2. If the protocol server does not respond in the format that is defined by the File Synchronization via SOAP over HTTP Protocol or it responds incorrectly, OneNote 2013 or OneNote 2010 use either of the following, depending on the version of the operating system on which it is running:

• If it is running on Windows Vista operating system or Windows 7 operating system, OneNote 2013 or OneNote 2010 use the Web Distributed Authoring and Versioning (WebDAV) Protocol Client Extensions.
• If it is running on Windows XP operating system, OneNote 2013 or OneNote 2010 uses the FrontPage Server Extensions Remote Protocol.

The following table describes the additional protocols used by OneNote 2013, OneNote 2010, or Office OneNote 2007 when synchronizing files with servers running Windows SharePoint Services.

For a complete reference of Microsoft Office Protocols, check out http://msdn.microsoft.com/en-us/library/cc307282%28v=office.14%29.aspx

About OneNote Notebook Synching

When you work in notebooks that are stored on your computer, Microsoft OneNote 2010 continually and automatically saves your changes as you work. However, if you set up a shared notebook on the Web or your organization’s network in order to share the notebook on other computers or with other people, saving and managing changes occurs a bit differently.
OneNote keeps a local cached copy of a shared notebook on each computer that accesses it and then periodically synchronizes any changes with the notebook files that are stored in the shared location. You can adjust the settings that control this process.

OneNote 2010 does do incremental syncing on notebooks. But if a file is an embedded file, such as a video, if that file changes, then the entire file would need to be uploaded again.
There is not a way to change the syncing interval of notebooks.

Notes About SharePoint & OneNote

Unlike Microsoft Word and Microsoft PowerPoint, Microsoft OneNote stores version information within the file itself. For this reason, administrators should follow these recommended practices when storing OneNote notebooks in a SharePoint Server document library:

• Do not enable minor versioning. This is the default setting in SharePoint Server 2010.
• If major versioning is enabled, set a reasonable maximum number of versions to store. By default, major versioning is not enabled in SharePoint Server 2010.

It should be understood that in SharePoint 2010 there are at 8 methods of data manipulation possible. See http://nikspatel.wordpress.com/2012/08/05/sharepoint-2010-data-querying-options-server-om-vs-client-om-vs-rest-vs-linq-vs-search-api/

Considering this, when the question comes up “How is OneNote pegging my SharePoint server resource-wise and what can I do to limit that”, one needs to carefully review the SharePoint access methods in comparison to the particular mode OneNote is communicating in.

As synched OneNote content is delivered via Office Web Application, all the standard SharePoint Resource Throttling approaches will apply – including being able to offload heavy queries to certain times of day. This is also the same for SharePoint Workspace (although there are some other built-in limits at play in Workspace) and a variety of third-party apps such as SharePlus.

Notes About Office Web Application Service Limits

This includes the Word Web App, PowerPoint Web App and OneNote Web App. There are several different perspectives that you have to look at each of these. Specifically you should focus on viewing versus editing because the resources required are quite different.

The drivers for performance are expected concurrent users and what type of operations are going to be done. Microsoft’s initial recommendations are 100 daily users with average of 10 concurrent can be supported by 1 WFE and 1 App Server. Going to 1000 daily and 30 concurrent would require 2 WFE and 2 App servers. Going to 10,000 daily and 300 concurrent would require 4 WFE and 3 app servers.
Much of the limits associated to OneNote Services are directly tied to the limits for list and libraries. This is because each section in OneNote is stored as folders and documents in a library.
The maximum size for each section of an OneNote section is again driven by the file size limits for lists and libraries.

If there are embedded images, files, etc. in OneNote, that are greater than 100KB, they will be split out into their own binary files within the SharePoint library.

Error Codes

The full reference to possible OneNote errors can be found here: http://msdn.microsoft.com/en-us/library/ff966472.aspx

Incoming search terms:

• sending onenote data to sharepoint 2013 list
• set-sp 200mb sharepoint development sql memory command
• sharepoint 2013 error in central administration root element of w3c xml schema secure store
• to activate intellinsense in MS-Excel

A useful collection of info regarding co-authoring in SP 2010:

“In today’s highly connected work environment, documents created by multiple authors, editors, and stakeholders are becoming the rule, instead of the exception. Organizations look to the communication and collaboration capabilities of Microsoft SharePoint Server 2010 to help them foster communication and collaboration between end-users while reducing administration required to support it. Microsoft Office 2010 continues this trend with co-authoring functionality for Microsoft PowerPoint 2010, Microsoft Word 2010, and Microsoft OneNote 2010 documents on SharePoint Server 2010.

Co-authoring removes barriers to server-based document collaboration and helps organizations to reduce the overhead associated with traditional document sharing through attachments. Co-authoring simplifies collaboration by enabling multiple users to work productively on the same document without intruding on one another’s work or locking one another out. This functionality requires no additional server setup and is the default state for documents stored in SharePoint Server 2010. Co-authoring functionality is managed by using the same tools and technologies that are already used to manage SharePoint, helping to minimize the impact on administrators.”

• Co-authoring overview (SharePoint Server 2010)
  http://technet.microsoft.com/en-us/library/ff718249.aspx
• Co-authoring administration (SharePoint Server 2010)
  http://technet.microsoft.com/en-us/library/ff718235.aspx
• Configure versioning for co-authoring (SharePoint Server 2010)
  http://technet.microsoft.com/en-us/library/ff718246.aspx
• Configure the co-authoring versioning period (SharePoint Server 2010)
  http://technet.microsoft.com/en-us/library/ff718243.aspx
• Configure the maximum number of co-authoring authors (SharePoint Server 2010)
  http://technet.microsoft.com/en-us/library/ff718248.aspx
• Disable co-authoring (SharePoint Server 2010)
  http://technet.microsoft.com/en-us/library/ff718245.aspx

Incoming search terms:

• co authoring office 2013
• groove server co authoring
• sharepoint 2010 co-authoring fails
• sharepoint 2013 co-authoring

New (Oct.25 2012) release of the Microsoft All-In-One Code Framework is out.

Lots of new Windows Phone 8 samples, an Enterprise Sales Dashboard for Windows 8, SharePoint 2013 Custom Geolocation field type with Client side rendering, a Microsoft Surface Sample screen saver, and more..

Introduction

Developers love code samples. Samples often serve as the starting point for many developers to learn a new technology. They also provide straightforward solutions and helpful references when we as developers need to solve tough programming tasks. Some developers even live by code samples.

In partnership with Visual Studio Product Team and MSDN Samples Gallery Team, Microsoft All-In-One Code Framework releases Sample Browser Visual Studio Extension for Visual Studio 2012 and Visual Studio 2010 – an effort to evolve the code sample use experience. You can search and download 3500+ Microsoft official code samples and community samples, including over 700 Windows 8 samples and more than 1000 All-In-One Code Framework customer-driven code samples. With its integrated sample search, flexible sample download and more than ten useful features designed for easier access and management of code samples, we hope to put the power of tens of thousands of code samples at developers’ fingertips.

Features & Benefits

• Integrated and Rich Sample Search Experience

Sample Browser Visual Studio Extension is integrated with Visual Studio Quick Launch Bar, Toolbar, Code Editor and File Menu. It gives you quicker access to samples when you are writing code in Visual Studio. A rich set of sample search conditions allows you to filter search results by language, owner, technology and the targeting Visual Studio version.

• Integrated and Flexible Sample Download Experience

The Sample Browser Visual Studio Extension is integrated with the built-in support of downloading online samples in Visual Studio 2012. Code samples downloaded in Sample Browser Visual Studio Extension are visible to the built-in code sample feature in Visual Studio 2012. Vice versa.

Beyond that, Sample Browser Visual Studio Extension provides additional benefits to developers. Developers can enjoy theflexibility in downloading and managing code samples. By multi-selecting sample search results, and clicking a simple download button, you get your wanted code samples.

• Integrated Look and Feel

Sample Browser Visual Studio Extension is integrated with the Visual Studio theme colors. It supports both light and dark themes.

Incoming search terms:

• develop sharepoint 2013 solutions visual studio 2012 windows 8
• download visual studio 2012 extension for sharepoint 2013
• sharepoint 2013 visual studio 2012 target framework not selected
• sharepoint 2013 windows 8 development

Nintex Workflow utilizes the SharePoint workflow engine, which in turn is built on the Windows Workflow Foundation. Like with many aspects of SharePoint, there are certain performance limitations and common errors that can be encountered, not all of which are documented. This document has been compiled to address common issues that we have discovered over time such as workflows taking a long time to process, publish and start, as well as errors such as “Failing to start (retrying)”.

There are a number of different factors which can affect the performance and success of workflows, which are fully outlined. This document provides guidance on identifying, responding to and avoiding these issues.

Download (.PDF): http://connect.nintex.com/files/folders/23042/download.aspx

1 Contents ………………………………………………………………………………………………………………………… 1
2 Conceptual overview ………………………………………………………………………………………………………. 3
3 Workflow size and performance ……………………………………………………………………………………….. 4
3.1 The workflow takes a long time to start and/or publish ……………………………………………….. 4
3.2 Resources used when a workflow starts …………………………………………………………………….. 5
3.3 Workflows are failing with specific errors …………………………………………………………………… 5
3.4 Architectural considerations ……………………………………………………………………………………… 5
4 Common errors and issues ………………………………………………………………………………………………. 6
4.1 Common error messages ………………………………………………………………………………………….. 6
4.1.1 Cannot find a corresponding human workflow task ID for this task ………………………… 6
4.1.2 This task is currently locked by a running workflow and cannot be edited. ……………… 6
4.1.3 Failed to start (retrying) …………………………………………………………………………………….. 6
4.2 Common issues ……………………………………………………………………………………………………….. 7
4.2.1 Timeout errors when updating an item. ………………………………………………………………. 7
4.2.2 Multiple workflows accessing/updating an item at the same time …………………………. 8
4.2.3 Actions not displaying correctly in the workflow designer UI (Nintex Workflow 2007) 9
5 Key Nintex Workflow design factors in reducing system load ……………………………………………… 10
5.1 Task list issues and the amount of approval actions used ……………………………………………. 10
5.2 Certain actions have a heavier processing load ………………………………………………………….. 10
5.3 Delay actions (state machine/loops) ………………………………………………………………………… 10
5.4 Amount of concurrent workflow processes running/workflows starting at the same time 11
6 To split or not to split – preliminary considerations before breaking up a large workflow ……… 12
6.1 Increase the time-out of the timer service ………………………………………………………………… 12
6.2 Increase the SharePoint Workflow time-out: …………………………………………………………….. 13
7 Splitting a workflow process into smaller sequential workflows …………………………………………. 14
7.1 Advantages of splitting a workflow into separate sub processes ………………………………….. 14
7.1.1 Avoiding the repetition of a long, complex process …………………………………………….. 14
7.1.2 Ease of troubleshooting …………………………………………………………………………………… 14
Nintex – Workflow performance improvement and load reduction Page 2 of 22
7.1.3 Eliminating time-outs ………………………………………………………………………………………. 14
7.2 Disadvantages ……………………………………………………………………………………………………….. 15
7.2.1 Understanding your process at a glance …………………………………………………………….. 15
7.3 Approach to splitting………………………………………………………………………………………………. 15
8 Appendix 1 – How the “Commit pending changes” action works and when it is best used …….. 18
8.1 The “Commit pending changes” workflow action: ……………………………………………………… 18
8.1.1 Actions that are processed in the SharePoint batch …………………………………………….. 19
8.1.2 Actions that are processed in the Nintex batch …………………………………………………… 19
8.1.3 Hybrid actions ………………………………………………………………………………………………… 19
9 Appendix 2 – Checking performance on your server ………………………………………………………….. 21

Incoming search terms:

• GetRunningWorkflowTasks nintex
• merge nintex data workflow
• nintex workflow 2013 architecture with sharepoint
• nintex workflow failed on start
• nintex workflow failed on start retrying
• nintex workflow process task response 2
• Sharepoint 2013 workflow error

Here are the assets from my presentation last night to the Victoria SharePoint User Group, vSharePoint (view on Meetup.com). Thanks to Gerry Brimacombe from Sector Learning for hosting and Heidi Bergstrom for her detailed insight into how Government in BC uses SharePoint.

PowerPoint .PPTX Download: vSharePoint-SharePoint Performance Part 2
PowerPoint .PDF Download: vSharePoint-SharePoint Performance Part 2

TypeScript is a language for application-scale JavaScript development.TypeScript is a typed superset of JavaScript that compiles to plain JavaScript. Any browser. Any host. Any OS. Open Source.

http://www.typescriptlang.org/#Download

Starts from JavaScript, Ends with JavaScript

TypeScript starts from the syntax and semantics that millions of JavaScript developers know today. With TypeScript, you can use existing JavaScript code, incorporate popular JavaScript libraries, and be called from other JavaScript code. TypeScript compiles to clean, simple JavaScript code which runs on any browser, in Node.js, or in any other ES3-compatible environment.

Contribute

Read the specification in doc or pdf

Discuss and provide feedback on the language.

Play with the bits and file bugs.

Join the #typescript Twitter discussion and follow the CodePlex project.

Learn

Tutorial – Best way to get up to speed on TypeScript.

Forums – Great place to get help with using TypeScript.

Incoming search terms:

• claims authentication sharepoint 2013
• sharepoint 2010 claims based authentication
• typescript in Office 2013

For developers and consumers alike, successful W3C and Ecma International web standards are important for making the web better. A comprehensive test suite is an important part of a healthy standard, along with a clear specification and great implementations of the standard. Without thorough tests that assess the normative statements in a specification, a proposed standard is just a document on a website.

Any browser can claim to support some or all of a specification. The test results from a comprehensive test suite are the best way to determine which browsers will render the same markup consistently. Web developers have told us that seeing the test results, chapter-by-chapter, spec-by-spec, enables them to spend their valuable time building rich, interoperable web experiences for their customers.

We developed 75 new test cases and updated 168 test cases in conjunction with development of Internet Explorer 10 Release Preview. The IE Testing Center now offers a total of 7573 test cases. We continue to work closely with these two web standards organizations by submitting these test cases officially within each working group’s official process.

We welcome your continued feedback on the test cases using the appropriate W3C mailing list for each working group. For ES5 test cases please open bugs in the test262 bug database.

The first table below summarizes the test results by specification with Internet Explorer 10 Release Preview along with each of the major shipping browsers running on the Windows Release Preview. The second table at the bottom of this page provides links to each of the test cases we submitted to each appropriate working group to help the web become more interoperable.

Incoming search terms:

• sharepoint development standards
• ie10 test cases
• sharepoint system update cannot complete this action the cobalt error was thrown

Thought i’d share that there’s an IE port of a valuable plugin i’ve used in Firefox for a while, View Source Chart:

Steps to get beautiful, visually sensible HTML source viewing in IE9:
1. Copy the script below and paste it into a new browser bookmark.
2. Click the bookmark from any page to view its source chart.

For other browsers, check the first code block on this page.

About View Source Chart

Cross-browser bookmarklet now available at viewsourcechart.com

A PICTURE SAYS A THOUSAND WORDS
Eyesight is the most efficient way for the human brain to process information. By placing visual boundaries where they already exist invisibly, Source Charting enables you to take in DOM structure and hierarchy as fast as your brain possibly can.

IT’S BETTER BECAUSE…
When mentally building tag boundaries by reading a tag name, then using manual actions like clicking, finding and scrolling, we experience forced breaks in cognitive processing. As the DOM becomes more complex, more productivity is lost. It doesn’t take long before mentally navigating the DOM becomes impossible.

Source Charting eliminates the need for processing any other way but the fastest: visually. It provides an instant and complete visualization of hierarchical nesting of any tag in the view port.

SUMMARY
Source Charting…
* Defines HTML Tag Boundaries (so you don’t have to)
* Defines DOM Structure and Hierarchy (so you don’t have to)

Case In Point: The Misapplication of Flowchart-style UI for DOM Inspectors
DOM inspectors and Folder Viewers have historically (and mistakenly) used flowchart-style GUIs to help users navigate hierarchies. The problem is that this type of GUI is intended to convey sequential movement or flow, not structure.

Because sequence and flow is measured one step at a time, the lines connecting elements in a flowchart-like GUI span only one generation (parent-child). When used to depict complex hierarchical structures like the DOM, the user is forced to inefficiently and inaccurately measure hierarchical nesting levels using white space indentation. (See image #3 above)

It is precisely this subtle but monumental mistake that View Source Chart overcomes.

The only way to visualize structure accurately is to measure hierarchical nesting. This is done simply by pictorially delineating element boundaries, which results in a manifestation of document structure.

For a full de-bugging How-To, visit http://viewsourcechart.com/what-why-how

Cross-browser bookmarklet available at http://viewsourcechart.com/get-the-bookmarklet

Incoming search terms:

• sharepoint 2013 css chart
• cascading style sheet reference sharepoint 2013
• sharepoint 2013 css guide
• sharepoint 2013 style sheet