Partilhar via

Preparing for TechEd Europe while doing last part of local road show

  • Artigo

Two weeks ago we started with our local road show called Big>Days through Austria. For our developer track I have prepared three sessions full of "exploring new things of Visual Studio 2005 and .NET 2.0" and Alex has prepared a session about SQL Server 2005. While today we start traveling to the last two locations, Linz and Graz, this week, I have uploaded my persentations for Teched Europe in Amsterdam.

In Amsterdam I'll talk about the experience I made with developing Office 2003 solutions with Smart Documents and XML integration (I have worked on a huge proof of concept in this space with one of our largest ISVs, Data Systems Austria). This is the session's abstract:

Developing Real World Smart Documents with .NET
Smart Documents provide an infrastructure for creating task panels running within Microsoft Word 2003 and Microsoft Excel 2003. By leveraging different backend systems through the XML capabilities of Microsoft Office 2003 they finally assist information workers with the creation of business documents. While developing a basic Smart Document is fairly easy there are some key success factors for sophisticated solutions. Apart from fundamentals like dealing with the document’s life cycle this session covers key topics for successfully creating Smart Document solutions: Designing appropriate XML schemas, managing state across multiple document instances and creating reusable UI code and XML schema types. All this will be based on a sample framework which has been developed for a real world application. Learn the key success factors for developing Smart Document solutions with Visual Studio .NET 2003/2005 and start making information workers life easier.

In this session I'll cover how to develop smart documents (VS 2003 with the framework we have developed in the proof of concept (it's already in production for the ISV) and VS 2005) and then put all the things together through talking about the key success factors: correct XML schema design for documents (which is inherently different from "message" schema design) and how you can design your components for reusability.

Comments