Sneak Preview of Project Gemini

Continued here:
Sneak Preview of Project Gemini

On the topic of “teasers”, one of the things we’ll be talking about in the coming weeks is project Gemini.  I won’t get into the details just yet (otherwise it wouldn’t be a teaser), other than to say it’s a powerful data analysis feature, it’s an add-in to Excel (i.e. not a built-in Excel feature), and it’s the result of collaboration between the Excel and SQL teams.  The BI Blog has been covering all news related to Gemini .  From the BI Blog, here are a couple sneak peak videos : BI Power Hour: Sneak Preview of Gemini – part 1 Get a sneak preview of the new functionality for BI within Excel with Project Gemini. This demo shows how you can quickly analyze massive amounts of data, create connections to data, and share insights all within the familiar Excel environment

Copying a Document to the End User Computer after a ClickOnce Installation (Mary Lee)

Starting in Visual Studio 2010 Beta 1, you can perform additional tasks after an Office solution is installed known as a post-deployment action. For example, you can copy a customized Office document and create registry keys on the end user computer

See the original post: 
Copying a Document to the End User Computer after a ClickOnce Installation (Mary Lee)

Deploying Multiple Office Solutions In a Single Installer (Mary Lee)

Starting in Visual Studio 2010 Beta 1, you can deploy multiple Office solutions in a single ClickOnce installer. For example, you can develop two Office solutions (one for Outlook and another for Excel) and combine these into a single installer with a single entry in the Add/Remove Programs list in Windows XP and the Programs and Features list in Windows Vista.

View original here:
Deploying Multiple Office Solutions In a Single Installer (Mary Lee)

8. VSTO Bug Tracker : Using a Ribbon

To get started, from the Project menu choose Add New Item. In the Add New Item dialog box, click Ribbon (Visual Designer)

Read the original post: 
8. VSTO Bug Tracker : Using a Ribbon

7. VSTO Bug Tracker : Using Document-Level Features in Add-Ins

Prior to Visual Studio 2008 SP1, you couldn’t use common VSTO features like controls in the document and databinding to list objects at the add-in level.  But with SP1 we introduced a way for you to use these features at the add-in level.  In this section some of the wierd ways Idid things in section 4 will start to make more sense—I designed the code in Section 4 to be easily portable to an add-in. One thing that won’t port to the add-in level is cached data—that feature only works when code is at the document level. Choose File > Add > New Project.

Read the original post:
7. VSTO Bug Tracker : Using Document-Level Features in Add-Ins

6. VSTO Bug Tracker: Word Report Generation

Another thing I want my bug tracking system to do is help me generate a weekly report with a summary table of key stats for all my teams. I want to do this in Word so I can add my own comments and a status summary of what went on during the week. We already prepared to build this Word report by writing the Web Service method “GetDailyValues”.  Create a new Word document project in C# and call it BugDocument.

Here is the original post: 
6. VSTO Bug Tracker: Word Report Generation

5. VSTO Bug Tracker : Using Cached Data

We are now going to convert our previous sample to use cached data.  In our current solution we have code that when the document loads, it calls a web service to get the bug data.  We are going to use the cached data feature to allow us to call the web service at a different time to fill in the dataset in the document without having to start Excel.  Why would we want to do this?  Well, several reasons.  First, we can improve the load time of our document by updating the data in the document in advance.  This also is handy to update the data in the document if the document is going to be opened outside the firewall where the web service can’t be accessed.  So a process running on a machine within the firewall can update the data in the document and then give the document to a machine running outside the firewall. As mentioned in the last article, it can also allow me to update the bug data in my workbooks in the middle of the night via a scheduled process so I can hit the web service when traffic is low.

Originally posted here:
5. VSTO Bug Tracker : Using Cached Data

4. VSTO Bug Tracker : Getting the data into Excel

The next step is to get more of the bug data into Excel so we can start to analyze it.  To do this, we will use VSTO’s data bind to ListObject support. I’m going to approach this in a different “more advanced” way that will make sense later in the demo. Long time VSTO developer will know that the simple way to bind data to a list object in VSTO is to create an Excel Workbook project, add a data source, then drag and drop the data source onto the Excel Workbook

See more here: 
4. VSTO Bug Tracker : Getting the data into Excel

Creating a Research Service for Word 2007 in C# with Visual Studio 2008

This post examines how to build research services for Word and other Office applications.

Here is the original:
Creating a Research Service for Word 2007 in C# with Visual Studio 2008

Converting existing Office COM add-in projects to Add-in Express

Last week I had a chance to check out how easy the conversion process is.

Read more:
Converting existing Office COM add-in projects to Add-in Express