Creating a SharePoint Visual Web Part using Visual Studio 2010

Last year we built a business application for order management for Northwind Traders on the Office and SharePoint platform using Visual Studio 2008 and Office & SharePoint 2007. Lately I’ve been writing articles that show how to upgrade it to Office & SharePoint 2010 using Visual Studio 2010. If you missed them: Migrating an Outlook Client to .NET Framework 4 in Visual Studio 2010 Build WPF Data Controls for Outlook Addins Easily with VS2010 Migrating a 2007 Workflow to Visual Studio & SharePoint 2010 I also released the migrated sample application here: http://code.msdn.microsoft.com/OBANorthwind If you look at the VS2010 solution in that sample you’ll see a few extra projects in there that add more functionality to our application

Read the original here:
Creating a SharePoint Visual Web Part using Visual Studio 2010

Simple Tip when creating VS projects for sharepoint 2010

One thing I’ve noticed is that when you create a SharePoint project in VS 2010 (File, New, Project) and create a name for your project it doesn’t get persisted down to the project item. For example, create a new Visual Web Part project; you’ll notice that your default naming convention follows VisualWebPart1 for the web part that is added to the default top-level SharePoint project.  If you create a new Visual Web Part project called MyFirstVisualWebPart you’ll see that the ensuing project item that’s created does not prompt you for a name for your web part

Original post:
Simple Tip when creating VS projects for sharepoint 2010

Open XML SDK Code behind the Custom XML Markup Detection Tool

On Brian Jones’ blog today, Zeyad Rajabi has posted the source code for the Custom XML Markup Detection tool from my last post.

Continued here: 
Open XML SDK Code behind the Custom XML Markup Detection Tool

New Office 2010 Developer Video

We just published a new video on MSDN that provides a great starting point for understanding what we’re talking about when we speak about “Office 2010 productivity solutions”. You can watch the video (~7 minutes long) by clicking the image below: http://go.microsoft.com/?linkid=9709532 At the end of the video I discuss where you can go to get started with developing Office solutions.

View original post here:
New Office 2010 Developer Video

Scanning Tool to Detect Custom XML Markup in .DOCX and .DOCM files

Quick Start The Installer is located here .  Background reading What is Custom XML- … and the impact of the i4i judgment on Word , Regarding Custom XML Patch distribution and availability , Associating Data with Content Controls , Using Content Controls vs. Custom XML Elements , After we made a patch available for Word related to the recent court ruling, we were asked by a handful of customers if there is a way to identify document files or solutions which may be affected.

View original here: 
Scanning Tool to Detect Custom XML Markup in .DOCX and .DOCM files

Sample: Converting Word Documents to PDF using SharePoint Server 2010 and Word Automation Services

Explore the code in this visual how-to article as you learn how to programmatically convert Word documents to PDF format on the server by using Word Automation Services with SharePoint Server 2010. Author: Joel Krist (MVP)

Here is the original post: 
Sample: Converting Word Documents to PDF using SharePoint Server 2010 and Word Automation Services

Northwind Office Business Application Updated for Visual Studio, Office & SharePoint 2010

Last year we built a business application for order management for Northwind Traders on the Office and SharePoint platform using Visual Studio 2008 and Office & SharePoint 2007. Recently I started releasing articles that show how to upgrade the VS2008 version to VS2010: Migrating an Outlook Client to .NET Framework 4 in Visual Studio 2010 Build WPF Data Controls for Outlook Addins Easily with VS2010 Migrating a 2007 Workflow to Visual Studio & SharePoint 2010 Today I updated the sample with some more goodies including some SharePoint 2010 web parts that I’ll write about soon

Go here to see the original: 
Northwind Office Business Application Updated for Visual Studio, Office & SharePoint 2010

Reading Data from External List using the SharePoint 2010 Client Object model

One of the demos I showed this week was the integration of the new SharePoint 2010 client object model (SP COM) and an external list. The SP COM is a way to work with lists where you create and execute batch commands against your SharePoint 2010 server. You can find more information here: http://channel9.msdn.com/learn/courses/SharePoint2010Developer/ClientObjectModel/ .

Read the rest here:
Reading Data from External List using the SharePoint 2010 Client Object model

Sample: Manipulating Multiple Exchange Accounts in Outlook 2010 (Visual How To)

Explore the code in this visual how-to article as you create an add-in to manipulate multiple Exchange accounts that are configured in a single Outlook 2010 profile. Author: Brian Randell (Other)

Excerpt from:
Sample: Manipulating Multiple Exchange Accounts in Outlook 2010 (Visual How To)

Word Automation Services: How it Works

In my first two posts in the series on Word Automation Services, I talked about what it is and what it does – in this post, I wanted to drill in on how the service works from an architectural standpoint, and what that means for solutions built on top of it. Word Power on the Server The most important component of Word Automation Services is getting a core engine with 100% fidelity to desktop Word running on the server – accordingly, much of our effort was focused on this task.

Read more from the original source:
Word Automation Services: How it Works