MSDN Magazine May 2008

See how to build a document-level Visual Studio Tools for Office customization and integrate it with a content type in SharePoint.

Learn how to automate custom SharePoint application deployments, use the SharePoint API, and avoid the hassle of custom site definitions.

Kenny Kerr sings the praises of the new Visual C++ 2008 Feature Pack, which brings modern conveniences to Visual C++.

One-time passwords offer solutions to dictionary attacks, phishing, interception, and lots of other security breaches. Here's how it all works.

Here we present a rundown of the various language paradigms of CLR-based languages via short language introductions and code samples.

Editor-in-Chief Howard Dierking explains why it's wise to consider Microsoft Office a development platform, even though developers typically don't.

This month the Toolbox column takes a look at database logging, Joel Spolsky's blog, printing code projects, and ASP.NET reading.

In the second of a two-part series, Vance Morrison delves into the meaning of performance measurements, explaining what the numbers mean to you.

The Entity Framework is a hot topic, but how do you know when to use EntityClient, Object Services, Entity SQL, or LINQ? Find out here.

This month we begin a look at the Single Page Interface (SPI) model and some design patterns for designing AJAX applications.

Did you know you can use Windows PowerShell to perform lightweight request/response testing for an ASP.NET Web app? Here's how.

See how to use Word to capture a VBA macro and use Visual Studio Tools for Office to wrap it up into a deployable Word add-in.

As we'll show, with just a few lines of JavaScript you can build a general-purpose framework for incorporating page turns into Silverlight 1.0 apps.

When building workflows, you must consider the developer experience, available tools, long-term maintenance, and future versioning.

In this installment of Security Briefs, James Whittaker explains the rules and the pitfalls of penetration testing so you'll know how to avoid them.

Use the Team Foundation Server EventService to create and manage event subscriptions or create a Web service to receive and process events.

Rich or reach, rich or thin, thick or fat? Thus went the battle over how much functionality a client should have. Here's how it all turned out.