Are you an ASP.NET developer who is ready to learn more about SharePoint 2010? Visit the Getting Started page to view screencasts and hands-on labs about working with SharePoint 2010 developer features that are familiar to ASP.NET developers, such as Web Parts and workflow.
Read more here:
Get Started Developing on SharePoint 2010
It’s time to think of Office and SharePoint as a platform.
In this interview, Reza Chitsaz, Senior Program Manager for Microsoft Visual Studio Business Applications, discusses his team’s efforts to bring professional .NET developers the ability to write managed code on the Office platform. Learn about innovative customization scenarios in Outlook, as well as the huge leap forward in the developer experience building solutions on top of SharePoint
See original here:
Microsoft Visual Studio Tools for Office 2010
I am pleased to announce the availability of the PST File Format SDK . The PST File Format SDK provides a cross-platform C++ library for reading files using the Outlook Personal Folders File Format (.pst) Structure Specification .
Here is the original post:
Announcing the PST File Format SDK
Learn about the programmability enhancements in Microsoft Office 2010 from one of its creators. In this interview, Brian Jones, Group Program Manager for the Microsoft Office Solutions Framework Team, dives deep into the details
Original post:
VBA, Programmability, and Open File Format for Office 2010 with Brian Jones
The Microsoft® SQL Server® 2008 R2 Feature Pack is a collection of stand-alone packages which provide additional value for Microsoft® SQL Server® 2008 R2.
Read more here:
Microsoft® SQL Server® 2008 R2 Feature Pack
Using SketchFlow to create a website prototype
Read the original post:
Using SketchFlow to create a website prototype
Managed Office add-ins traditionally have been able to run in the targeted application (the version of the application whose PIAs the add-in references) and in later versions of the application. Therefore, if you need to create a single VSTO add-in that can be run in multiple versions of an application, the typical guidance is to develop the add-in by using a project template for the oldest version of Office that you want to support. For example, if your add-in needs to work with Office 2003 and Office 2007, you should create an Excel 2003 add-in (by using VSTO 2005 SE with Visual Studio 2005, or by using Visual Studio 2008). However, this strategy has several inconveniences: If you want to test/debug/run the add-in on your development computer, you must have the earliest version of Office you are targeting installed
Go here to read the rest:
Creating an Add-in for Office 2007 and Office 2010 that “Lights Up” on Office 2010 (McLean Schofield)
Chances are you’ve already read Brad Stevenson’s post Types of Solutions and you’re interested in building a BCS solution.
More here:
BCS Artifact Generator