Watch this video as you learn to create a BCS external content type for Office 2010 based on a Windows Communication Foundation (WCF) service.
This is the twenty-sixth in a series of blog posts I’m doing on the VS 2010 and .NET 4 release.
Debugging Tips with Visual Studio 2010
To continue the theme of landing external data in Office 2010, I’ve taken a demo excerpt from a session I presented at a conference last week to show how easy it is to land OData information in an add-in. In this sample I simply use the Northwind Database which is a publicly available OData producer .
Accessing an OData Producer using an Office 2010 Add-in
Every developer deserves a fantastic development environment that allows them to write, understand, navigate, and debug code as efficiently as possible. After all, developers spend most of their time in the IDE. As we designed and built Visual Studio 2010, we let this principle guide the product, and I think we've delivered an IDE that raises the development experience bar significantly. Starting today and over the coming weeks, I will highlight my favorite productivity features in Visual Studio 2010. Some of them are small features, and some of them required a large, coordinated effort across the team, but each one makes developers' lives a little easier
VS 2010 productivity improvements – Part I
Extends Visual Studio to enable the creation, configuration, building, debugging, running and packaging of scalable web applications and services on Windows Azure. Installation includes the Windows Azure SDK.
See the original post:
Windows Azure Tools for Microsoft Visual Studio
Good news! Project 2010 supports custom task panes! Bad News! Getting one to appear in a Project 2010 is not so obvious. Good News! It’s a lot easier than I make it sound. In this post, I’ll show you how to add a custom task pane to Project 2010 by using a Project 2010 or Project 2007 project template in Visual Studio.
View original post here:
Add a Custom Task Pane to Project 2010 (Norm Estabrook)
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
Simple Tip when creating VS projects for sharepoint 2010
Lately I’ve been converting an Office business application we built last year with Visual Studio 2008 to Visual Studio and Office 2010. Last couple posts we tackled converting the Outlook client piece.
As you probably know, Visual Studio 2010 was announced last week and it contains a lot of great features and project templates for SharePoint developers. Below is a short overview for some of the SharePoint development related features and project templates
Here is the original:
Short Overview of SharePoint Features in Visual Studio 2010