This ribbon button has been functioning great for the past 5 months and without any apparent change, it stopped working by throwing an error that “The Operation Failed“.

I found one workstation that was still able to submit using the same custom button. This workstation sees very little use and had not been rebooted in months. I rebooted this computer and as soon as it came back, the ribbon button was now returning the same error as the other computers.

This raised a flag for me that there might have been a change in the computers themselves and it was not a change in SharePoint that was breaking the functionality. I started to look through the recent Windows Updates that had been applied and noticed many updates, but one in particular was specific to Outlook 2010: KB2687623 Outlook 2010 update: November 13, 2012. I retracted this update and just like that the functionality was restored.

Now this update documents the following changes: (Link to KB article)

Issues that this update fixes

• When you connect to the Microsoft Office 365 Exchange Online service by using an expired password, Outlook 2010 enters a disconnected state. However, you do not receive a notification that states that the password expired.
  Note After you install this hotfix, a dialog box appears before the password expires. The dialog box lets you open a URL to change your password. For more information about Outlook password expiration, click the following article number to view the article in the Microsoft Knowledge Base:
  2745588
        (http://support.microsoft.com/kb/2745588/ )

  Outlook password expiration notification in Office 365

• Assume that Outlook 2010 is displayed in a right-to-left language such as Arabic or Hebrew. Additionally, assume that you press Ctrl, you right-click the Outlook icon in the notification area, and then you click Connection Status. In this situation, the content in the Microsoft Exchange Connection Status dialog box is not displayed correctly.
• When you accept a meeting request in certain time zones, Outlook 2010 crashes. 
• Note This issue occurs in the Jerusalem time zone.

Obviously this update fixes issues that are unrelated to our problem at hand. For future reference, it is always a good idea to verify each update prior to pushing it enterprise-wide. It might cause less head-aches down the road.

UPDATE: A comment left by SWRadio indicated that the update to Outlook 2010 KB2597090 (2/2013) also breaks the VSTO remote SaveAs() functionality. This one can also be removed from your system. Thanks SWRadio.

In the mean time, if you need them and have access to MSDN, click here to get directed automatically: https://msdn.microsoft.com/en-us/subscriptions/securedownloads/#ProductFamilyId=498

Make your language selection on the quick-launch menu on the left.

http://nikspatel.wordpress.com/2012/10/13/understanding-sharepoint-2010-experience-in-sharepoint-2013/

Visual Studio 2012 also offers the dual development tracks.

This, combined with the SharePoint 2010 Experience in SharePoint 2013 will make for a pleasant development experience.

• They provide users with the easiest discovery, purchase, and installation process.
• They provide administrators with the safest SharePoint extensions.
• They provide you with the simplest marketing and sales system based on a Microsoft-provided online app store.
• They maximize your flexibility in developing future upgrades.
• They maximize your ability to leverage your existing non-SharePoint programming skills.
• They integrate cloud-based resources in smoother and more flexible ways.
• They enable your extension to have permissions that are distinct from the permissions of the user who is running the app.
• They enable you to use cross-platform standards, including HTML, REST, OData, JavaScript, and OAuth.
• They enable you to leverage the SharePoint cross-domain JavaScript library to access SharePoint data. Alternatively, you can use a Microsoft-provided secure token service that is OAuth-compliant.
• They can extend SharePoint Online websites as well as on-premises SharePoint websites.

Of course, farm solutions are still required in some instances where you need to run code on the server directly. The app model does not allow running code on the Server object model but uses the following APIs to access SharePoint:

• SharePoint REST/OData service to access SharePoint sites, lists, and other data.
• SharePoint JavaScript, Silverlight, or .NET Framework client object models.
• On Windows Phones, you can use the SharePoint Windows Phone object model. 

The general guide is that farm solutions are still used for administrative type solutions that would deploy timer jobs, central administration features, PowerShell commands, etc. anything that would be of WebApplication, Farm, or Site Collection scoped. A guiding principle being that apps are for end-users and farm solutions for administrators.

SharePoint 2013 now blends the old search components with the FAST search components into one standard product. About 80% of FAST Search was embedded in the SharePoint Search platform, representing the most used features of FAST Search. *Update* The Standard CAL of SharePoint only integrates a subset of the FAST search features (Thanks to Niraj for pointing this out)*

The following diagram illustrates the new search server logical architecture:

The architecture of the search service breaks down in the following components:

Crawl Component:

Content Processing Component:

 Tracks crawled content and how users interact with the search results. It replaces the Web Analytics service form SharePoint 2010 to track usage of site content, passing this information back to the Content Processing Component to add to the search index, improving search relevance.

Index Component:

Accepts operations from both the content processing component by storing results of the item parsing in the index files, and from the query processing component by providing result sets. It is in charge of managing the indexed content when the architecture is changed by the search administration component.

Query Processing Component:

The query processing component receives a query from the end user, performs analysis,  linguistic processing like word breaking, stemming, query spellchecking, thesaurus, attempts to optimize precision, recall and relevancy. This optimized query is sent to the index component, and the returned result set is again processed further before being sent back to the search front-end.

Search Administration Component:

http://sharepoint.microsoft.com/en-us/Preview/sharepoint-requirements.aspx

https://profile.microsoft.com/RegSysProfileCenter/wizard.aspx?wizid=f2648d40-84ce-4556-8545-93d52a3253f2&lcid=1033&ci=393

Expect more posts in the near future now that the NDA is lifted on SharePoint 2013.

I’ve been in the RDP program for a while, hence the limited blogging here. Now that the gates are open, more will be posted here. Stay tuned!

Requirements for SharePoint 2013:

Software Requirements

Windows Server 2008 R2 Service Pack 1 or Windows 8 Server

Prerequisites

• Windows Identity Foundation v1.1
• Microsoft Information Protection and Control Client
• Microsoft WCF Data Services
• Windows Management Framework 3.0
• Application Server Role
• Web Server (IIS) Role
• Microsoft .NET Framework 4.0
• Update for the .NET Framework 4 (KB2468871)
• Microsoft SQL Server 2008 Native Client
• Windows Identity Foundation (KB974405)
• Microsoft Sync Framework Runtime v1.0 (x64)
• Windows Server AppFabric

Database Servers

Microsoft SQL Server 2008 R2 (Service Pack 1) 64bit or Microsoft SQL Server 2012 (64bit)

Here are the extensions:

	Visual Studio 2010 SharePoint Power Tools Templates and extensions that provide a sandboxed Visual Web Part together with enhanced support for sandboxed compilation to help you develop SharePoint solutions even more productively.
	Mavention SharePoint Assets Minifier Installs custom tools for minifying SharePoint assets such as JavaScript and CSS files.
	CKS – Development Tools Edition (Server) The SharePoint 2010 Visual Studio 2010 Extensions project (CKSDEV) is a collection of Visual Studio templates, Server Explorer extensions and tools providing accelerated SharePoint 2010 development based on Microsoft’s new SharePoint 2010 development tools.
	Free Taxonomy Editor For SharePoint Dotspine provides you a graphic modeler to easily design and populate taxonomy tree. Then you can export them as XML files to be proceeded by PowerShell and target SharePoint 2010.
	caml.net.intellisense Provides enhanced IntelliSense support for the Collaborative Application Markup Language (CAML) used by SharePoint.
	SharePoint Timer Job Item A SharePoint project item for creating timer jobs that have an associated configuration screen in Central Administration
	MP.SPDevExt The MP.SPDevExt Visual Studio 2010 Extensions project is a collection of Visual Studio item templates used to expedite the SharePoint 2010 development. It contains following item templates: Custom Field Type, Sandbox Solution Validator and Sandbox Workflow Action
	Silverlight SharePoint Web Parts An extension for adding Silverlight web parts to SharePoint features.
	Visual Studio 2010 Productivity Power Tools (Not specifically SharePoint) A set of extensions to Visual Studio Professional (and above) which improves developer productivity.
	Web Standards Update for Microsoft Visual Studio 2010 SP1 (CSS3, HTML5) (Not specifically SharePoint) Adds CSS3 support and updates the HTML5 intellisense and validation including new JavaScript API’s
	LINQ to SharePoint DSL Extension for Visual Studio 2010 This new feature is an extension to Visual Studio for modeling LINQ to SharePoint entities directly in VS2010. With this tool, it’s become possible to add a new kind of item in a VS project, that we name a LINQ to SharePoint schema.
	CodeMaid (Not specifically SharePoint) CodeMaid is an open source Visual Studio extension to cleanup, dig through and simplify our C#, C++, XAML, XML, ASP, HTML, CSS and JavaScript coding.
	Imtech Create Page Layout Content Type Extension Installs a Content Type Extension that allows you to generate a Page Layout from an existing Content Type.
	PowerCommands for Visual Studio 2010 (Not specifically SharePoint) PowerCommands 1.0 is a set of useful extensions for the Visual Studio 2010 IDE.

http://www.simple-talk.com/dotnet/.net-tools/managing-itemupdating-and-itemupdated-events-firing-twice-in-a-sharepoint-item-event-receiver/

Declared Record + 1 Day      Move to Recycle Bin

You will notice that the retention policy does not run as expected. This is normal behavior because there are two timer jobs that need to run sequentially to achieve the desired result and by default both these timer jobs are set to run on a weekly schedule. These are the timer jobs that need to be run:

• Information management policy
• Expiration policy

To allow for your short-term retention policies to work properly, you need to change their schedule to run daily:

1. Go to Central Admin
2. Monitoring
3. Review job definitions
4. Look for “Information management policy” and click it
5. Change the radio button in the Recurring Schedule to Daily and set the time to run at midnight:
   
6. Click OK
7. Look for “Expiration policy” and click it
8. Change the radio button in the Recurring Schedule to Daily and set the time to run at 2 AM:
   

You can also use the Run Now button in both these timer jobs to test documents that should already have been disposed of.

An example of this would be: Multiple court case documents sitting declared as records in a record library, with document disposition rules that trigger disposition 3 years after the case resolution date.

There is no way you could have put in the case resolution date prior to the completion of litigation and the documents need to be in the record center to prevent tampering with.

You could build an interface in a web part or _layouts page that allows a user to input the case resolution date and the code behind will

1. undeclare all the records about this case
2. add the resolution date
3. redeclare the record.

At this point disposition rules would kick in and dispose of the document after the required time period.

The code used to declare and undeclare the records is as follows:

You need to add the following namespace:

using Microsoft.Office.RecordsManagement.RecordsRepository;

Then you need the following bits of code to run against all the documents that match the selected court case:

SPSecurity.RunWithElevatedPrivileges(delegate()
{
	using (site = new SPSite(siteurl))
	{
		using (spWeb = site.OpenWeb(webguid))
		{
			list = spWeb.Lists[listguid];
			if (list != null)
			{
				item = list.Items[itemguid];
				//Checking whether the item is a record or not
				if (item != null && Records.IsRecord(item))
				{
					Records.UndeclareItemAsRecord(item);     //undeclares the item as a record
					//UPDATE ITEM HERE
					Records.DeclareItemAsRecord(item);     //declares the item as a record
				}
			}
		}
	}
});

Update:

I just found an MSDN article that identifies anotehr option to updating records programatically. It makes use of the Records.BypassLocks method which is called using the following block of code:

using Microsoft.Office.RecordsManagement.RecordsRepository;

SPSecurity.RunWithElevatedPrivileges(delegate()
{
    Records.BypassLocks(myListItem, delegate(SPListItem item)
    {
        //Perform any action on the item.
    });
});

Hope this code will be helpful to you. Let me know in the comments or via Twitter.

There is more to come soon. Stay tuned!