Office Development with Visual Studio : Excel 2007

BUG: “Old format or invalid type library” error when automating Excel (Christin Boyd)

VSTO Team — Tue, 07 Jul 2009 01:54:33 GMT

A customer recently reported this bug when running their Shared Addin for Excel on French Windows.

Error: 0x80028018 (-2147647512)
Description: Old Format or Invalid Type Library

His solution worked great on English Windows, but gave errors in any other language. This is a known problem in Excel and there are a few workarounds that work depending on the way you’re writing your Excel Addin. Let me take you through the problem, variations on the problem, and different solutions depending on which Visual Studio project template you choose to start your Addin.

The bug was originally documented in a KB 320369 article, which gives detailed repro steps, explanation, and two workarounds with sample code. So why am I writing a blog post if the KB article covers everything? Three reasons.

Because we’re fixing the problem in CLR 4 and I want to encourage you to use one of the recommended workarounds in your current solutions so that you’re ready when your users upgrade to .NET Framework 4.
Also, there are parts of the KB article that are a bit confusing, so I’ll try to add some color commentary to help explain what’s causing the problem.
And third, these problems do not occur if you use VSTO 2005 SE, VSTO 3.0 (which ships with Visual Studio 2008), or Visual Studio 2010. I’ll explain why and how later.

The KB article describes the problem:

Error: 0x80028018 (-2147647512)
Description: Old Format or Invalid Type Library

You receive this error calling an Excel method when the following conditions are true:

The method requires an LCID (locale identifier).

You run an English version of Excel. However, the regional settings for the computer are configured for a non-English language.

If the client computer runs the English version of Excel and the locale for the current user is configured for a language other than English, Excel will try to locate the language pack for the configured language. If the language pack is not found, the error is reported.

The quote from the KB article is accurate, but can be confusing. It is very difficult to determine if the Excel method you want to call requires LCID or not. The Primary Interop Assembly (PIA) does not indicate whether or not the LCID is needed, however VBA does not hide the need for LCID. Part of the reason why Excel hasn’t changed its methods is to maintain back compatibility with all the VBA code in the universe.

Fixed in VSTO

VSTO implemented a fix in VSTO 2005 Second Edition (SE). You can read more about this fix in Eric Carter’s blog post. The fix is also in all subsequent versions of Visual Studio 2008 and will be in Visual Studio 2010. You know you are using “VSTO” when you create a new Project in Visual Studio and select an Excel <version number> Workbook, Excel <version number> Template or Excel <version number> Addin. The fix was not implemented in the Shared Addin template in any version of Visual Studio. If you create a WinForms, WPF, Web or console application that calls Excel, then you will see this bug on non-English Windows.

Workarounds

If you are using the Shared Addin template, a WinForm, WPF, Web or Console application with any version of Visual Studio, then you should use the KB 320369 article to solve the problem.

The workaround is to write explicit calls to set the thread’s culture before calling into Excel. You can then reset the culture back to what it was before after you are finished calling Excel.

Install the Multilingual User Interface Pack for your version of Office.

Execute the Excel method or property by using InvokeMember so that you can specify the CultureInfo for the call. For example, the following code illustrates how you can invoke the Workbooks object Add method with "en-US" as the CultureInfo:

Dim oApp As New Excel.Application()
oApp.Visible = True
oApp.UserControl = True
Dim oBooks As Object = oApp.Workbooks
Dim ci As System.Globalization.CultureInfo = New System.Globalization.CultureInfo("en-US")
oBooks.GetType().InvokeMember("Add", Reflection.BindingFlags.InvokeMethod, Nothing, oBooks, Nothing, ci)

Or, instead of the above bullet and code sample, set the CultureInfo prior to calling the Excel method, and then you can reset it after your Excel call:

Dim oApp As New Excel.Application()
oApp.Visible = True
oApp.UserControl = True
Dim oldCI As System.Globalization.CultureInfo = _
    System.Threading.Thread.CurrentThread.CurrentCulture
System.Threading.Thread.CurrentThread.CurrentCulture = _
    New System.Globalization.CultureInfo("en-US")
oApp.Workbooks.Add()
System.Threading.Thread.CurrentThread.CurrentCulture = oldCI

The .NET Framework 4 will solve this whole culture problem. Excel is not going to change its culture sensitivity because of the need to support backwards compatibility. Starting with CLR 4.0, when managed code calls into a COM component and an LCID is required, then the CLR will pass LCID = 1033. Note that this is how VBA passes LCIDs. This means that Visual Studio 2010 project templates for Excel Addins can stop wrapping all Excel projects with LCID proxy. In the future, when you use VS 2010 and .NET 4 to write your Excel automation programs from a Shared Addin, console, Winforms, WPF, or Web application, you won’t need to wrap your calls either.

-Christin Boyd, Program Manager & Misha Shneerson, Senior Developer

VSTO Bug Tracker (Eric Carter, Beth Massi)

VSTO Team — Mon, 18 May 2009 23:16:30 GMT

Eric Carter released a sample and series of articles based on his TechEd demo last week that shows you how to bring bug data from TFS into Excel and Word using VSTO so it can be further analyzed.

If you you went to TechEd but missed the session you can watch it here if you’ve registered:

Advanced Microsoft Office Word and Excel 2007 Development in Microsoft Visual Studio 2008 with Visual Studio Tools for Office

Everyone can download the sample here.

And don’t forget to check the VSTO Dev Center often for more news, articles, videos, and samples.

Enjoy,
-Beth Massi, Visual Studio Community

TechEd Sessions on Office Development

VSTO Team — Fri, 08 May 2009 00:16:02 GMT

If you’re going to TechEd in Los Angeles next week, then don’t miss these four sessions:

DTL03-INT Meet the Microsoft Visual Studio Team
Christin Boyd, Eric Carter, Paul Yuknewicz, Jay Schmelzer, Dustin Campbell, Jonathan Aneja, Luke Hoban, Igor Zinkovsky, Faisal Nasir, Harry Pierson, Lisa Feigenbaum
Mon 5/11 2:45 PM-4:00 PM | Blue Theater 1

OFC325 Building Custom Applications in Microsoft Office Outlook 2007
Ty Anderson, Damon Armstrong
Tue 5/12 2:45 PM-4:00 PM | Room 408A

DTL324 - Microsoft Visual Studio 2010 Overview for the Business Application Developer
Jay Schmelzer
Tue 5/12 4:30 PM-5:45 PM | Room 515B

OFC324
Advanced Microsoft Office Word and Excel 2007 Development in Microsoft Visual Studio 2008 with Visual Studio Tools for Office
Eric Carter
Thursday 5/14 1:00PM-2:15PM | Room 515A

Of course, there are a dozen other sessions that appeal to Office developers and SharePoint developers. These are the four that I highly recommend. Originally I was going to list the 3 not-to-be-missed sessions, but then I couldn’t drop any of these from my list, so we have 4 Must See Sessions!

If you’re not going to TechEd, then please click the links on these speakers’ names to read their blogs where the will eventually post some of their demo code. Expect the posts to happen the Monday after their sessions. In the case of Eric Carter, he would probably love it if you’d buy his book, Visual Studio Tools for Office 2007: VSTO for Excel, Word and Outlook. Or you could just download a zip file with all of the of code from the book here. That should keep you busy for a while. The explanations in the book really do add to the overall value. I should credit the co-author, Eric Lippert. Both men are brilliant and funny, and very modest. At the Holiday Party this year, Eric Carter got up to sing karaoke and astounded us all with a bouncy rendition of “Sesame Street.”

-Christin Boyd, Program Manager, Visual Studio

Video How Do I: Add Controls at Run Time in an Application-Level Project (Mary Lee)

VSTO Team — Tue, 10 Mar 2009 18:59:52 GMT

In Walkthrough: Adding Controls to a Worksheet at Run Time in an Application-Level Project, you can see to add host controls at run time in an application-level add-in by using Visual Studio 2008 SP1. This video is posted to the How Do I Videos - Visual Basic page, part of the Visual Basic Developer Center.

How Do I: Add Controls to a Worksheet at Run Time in an Application-Level Project?

Mary Lee, Programming Writer.

Why Can’t I Change the Update Path when Redeploying VSTO Solutions? (Christin Boyd, Kris Makey, Jeff Young)

VSTO Team — Wed, 17 Dec 2008 01:45:39 GMT

The other day I was asked about the automatic Updates feature of VSTO 3.0 deployment. In this scenario, he used the Publish Wizard in VS 2008 to create a Word document solution and the install manifest. Then a bunch of people used the Word document, and kicked off the installer which then copied things to their ClickOnce cache. Everything worked fine. Then he needed to make changes to the code, recompile, and somehow get the solution to all of his customers. Instead of using the Publish Wizard to create the update in the same server, he chose to use a different server path. The customers were unable to install the updates. He tried editing the custom properties of the document to change the install path to the new server, but it still didn’t work. Then he tried testing with a new, clean computer, and on that computer he was able to install from the new path and use the new Word document. He asked us why were the “old” users unable to get the update?

This question shows up on the Forum occasionally. “Why can I not change the update location of VSTO v3 Add-in or Document once it is installed?” (Or) “Why does VSTO continue to check in the old location even after I change location property on client machines that installed the old version?”

The Path to the deployment manifest is used as part of the Identity for an Add-in. During the First installation of an Add-in or Document, the Full Path is set and stored by the VSTO Runtime for that client machine. Once you have installed an Add-in changing the path in the registration will cause the Add-in to throw an Error. Once you have installed a customized Document, the code-behind will only check the original location and changes to the path stored in the document will be ignored (this is to allow copying a local version of a customized document that you installed from a remote location). In order to change the location that an Add-in or Document checks for updates, you must First uninstall the “old” version on the installed clients and then install from the new location.

Now, if you want to delve deeper, then keep reading this paragraph, or skip to the next one. The low-level explanation is that ClickOnce uses the solution path as part of its identity when storing solutions into the ClickOnce cache. You will get similar behavior in a CO-deployed Windows Application as well _unless_ you use the deploymentProviderURL (DPURL). Setting the DPURL can allow WinForms applications to change where updates are pulled from so that Server A (from which a solution was original installed) can be decommissioned and updates can be retrieved from Server B. VSTO does not support DPURL. Why not, you ask? At the time we were considering it during the development of VS 2008, the amount of development work-months required was more than the time we had remaining (DPURL has implications on migration of data from old solution to new solution, for instance). After much discussion, we decided to have the ClickOnce team throw an exception of a DPURL is set for VSTO solutions. At the start of development for VS 2010, we considered this feature again, but again this feature did not make our list of highest priority deployment features. We are implementing a lot of new deployment features for VS 2010.

In conclusion, the solution Path is used as part of the identity. You can’t change the update path after you've installed an Office solution. In a Windows solution, you can change the update path using DPURL. VSTO doesn’t support DPURL because we couldn’t fit that feature in the development schedule. The workaround is to uninstall the solution from the user’s computer when it is stuck pointing to an old path that you can’t update anymore and then reinstall with a new Install Path set in the Publish wizard. We recommend that you set your Install Path to a URL that you predict can stay the same for as long as your users will need updates.

This explanation applies to Word document and template solutions, and to Excel spreadsheet and template solutions.

I hope this blog entry is helpful! Please leave comments to this article if you have feedback.

-Kris Makey, Jeff Young, Christin Boyd, Mary Lee and Saurabh Bhatia contributed to this blog post

How Do I: Deploy Document-Level Office 2007 Solutions with Windows Installer? (Mary Lee)

VSTO Team — Thu, 02 Oct 2008 19:26:00 GMT

In Deploying an Office solution using Windows Installer, you read how to deploy document-level Office 2007 solutions with Windows Installer. As a follow up, you can now see how to add a Setup project to your VSTO solution and add a custom action to update custom document properties. This example uses Excel 2007, but you can apply these principles to any document-level customization.

Deploying Excel Document-level Customizations with Windows Installer

This video is based on the whitepaper: Deploying a Visual Studio Tools for the Office System 3.0 Solution for the 2007 Microsoft Office System Using Windows Installer (Part 2 of 2), where you can get the code and follow along step-by-step.

Mary Lee, Programming Writer.

How Do I: Deploy Application-Level Office 2007 Solutions with Windows Installer? (Mary Lee)

VSTO Team — Thu, 02 Oct 2008 19:21:33 GMT

In Deploying an Office solution using Windows Installer, you read how to deploy application-level Office 2007 solutions with Windows Installer. As a follow up, you can now see how to add a Setup project to your VSTO solution and create registry keys. This example uses Excel 2007, but you can apply these principles to any application-level add-in.

Deploying Excel Application-level Add-ins with Windows Installer

This video is based on the whitepaper: Deploying a Visual Studio Tools for the Office System 3.0 Solution for the 2007 Microsoft Office System Using Windows Installer (Part 1 of 2), where you can get the code and follow along step-by-step.

Mary Lee, Programming Writer.

How Do I: Add Smart Tags to Excel Workbooks? (Kathleen McGrath)

VSTO Team — Fri, 29 Aug 2008 01:35:00 GMT

With the release of Visual Studio 2008 SP1, you can now add smart tags to Excel by using an add-in. In this video, I show you how to add them to both a document-level customization and an add-in project.

How Do I: Add Smart Tags to Excel Workbooks?

This video is based on the topic: How to: Add Smart Tags to Excel Workbooks, where you can get the code and follow along step-by-step.

Create an Excel Shortcut Menu That Writes Selected Values to a Text File (Harry Miller)

VSTO Team — Fri, 22 Aug 2008 23:14:59 GMT

It doesn't take much code to add a command to a shortcut menu in Excel, but the menu objects have strange names so it's not intuitive, to me at least. The trickiest part is just sorting out how it's supposed to work, because it seems like it should be different from adding buttons to toolbars, but it really looks like that's what you're doing.

You can watch the video and make me happy, or you can just jump to the code example that's all given a little lower down. Thanks to McLean Schofield, programmer/writer and 3-star forum answer person, for this code example!

Duration: 3 minutes, 50 seconds.

Public Class ThisAddIn

Private WithEvents writeToText As Office.CommandBarButton
Private selectedCells As Excel.Range

Private Sub ThisAddIn_Startup(ByVal sender _
As Object, ByVal e As System.EventArgs) Handles Me.Startup

DefineShortcutMenu()
End Sub

Private Sub DefineShortcutMenu()

        Dim menuItem As Office.MsoControlType = Office.MsoControlType.msoControlButton
        writeToText = Application.CommandBars("Cell").Controls.Add(Type:=menuItem, _
            Before:=1, Temporary:=True)

        writeToText.Style = Office.MsoButtonStyle.msoButtonCaption
        writeToText.Caption = "Write to a Text File"
        writeToText.Tag = "0"
    End Sub

    Private Sub Application_SheetBeforeRightClick(ByVal Sh _
        As Object, ByVal Target As Microsoft.Office.Interop.Excel.Range, _
        ByRef Cancel As Boolean) Handles Application.SheetBeforeRightClick

selectedCells = Target
End Sub

Private Sub writeToText_Click(ByVal Ctrl As Office.CommandBarButton, _
ByRef CancelDefault As Boolean) Handles writeToText.Click

        Try
            Dim currentDateTime As System.DateTime = _
                System.DateTime.Now
            Dim dateStamp As String = _
                currentDateTime.ToString("dMMMMyyyy_hh.mm.ss")

            Dim fileName As String = System.Environment.GetFolderPath( _
                Environment.SpecialFolder.MyDocuments) & "\\" & _
                dateStamp & ".txt"
            Dim sw As System.IO.StreamWriter = New System.IO.StreamWriter(fileName)

            For Each cell As Excel.Range In selectedCells.Cells
                If cell.Value2 IsNot Nothing Then
                    sw.WriteLine(cell.Value2.ToString())
                End If
            Next
            sw.Close()
        Catch ex As Exception
            System.Windows.Forms.MessageBox.Show(ex.Message)
        End Try

End Sub

End Class

I Just Want to Format a Cell in My Excel Worksheet (Norm Estabrook)

VSTO Team — Tue, 03 Jun 2008 20:41:08 GMT

So you just want to write some code to format a cell in a worksheet. However, there isn't a help topic in sight that shows you how to do it. There may be a topic out there, but you don't have time to sift through the web searching for it. You're not alone. The forums are filled with questions about how to accomplish what might seem like a simple task - like formatting a cell. But the search for the right class, method or property to do it is not so simple.

A great way to get unstuck on some of these small but distracting issues is to use the Excel macro recorder. Start the recorder, pick a cell, format the cell, stop the recorder and then look at the code that Excel generates. The trickiest part is translating the VBA code to C# or VB so that you can use the code in your VSTO project. However, doing this can be a lot easier than searching the web and MSDN for a topic that shows you which specific class or property in the massive Excel object model you need to perform your task.

Let's take a look at an example scenario. All I want to do is format a cell as a percentage with 2 decimal places on the right side. The Macro recorder will show me which method or property I need to use.

To use the Macro recorder in Excel 2007, you have to enable the developer tab in the Ribbon. Click the round Office button and then click "Excel Options". Then select the "Show Developer tab in the Ribbon" as follows.

Start the macro recorder as follows:

Select a cell and then set your formatting options as follows:

Stop the macro recorder. Open the macro in the VBA editor as follows:

Grab the generated VBA. For example the VBA generated by the macro that I recorded looks like this:

Range("B2").Select
Selection.NumberFormat = "0.00%"

Ok this is good. Basically the code is selecting cell B2 and then setting the "NumberFormat" property of the selected range to a percentage with 2 right-side decimal positions. I just need to open my VSTO project and add code that gets the range for cell B2, and then sets NumberFormat property of that range to "0.00%" as follows:

[C#]

Excel.Range range1 = this.Range["B2", missing];
range1.NumberFormat = "0.00%";

[VB]

Dim range1 As Excel.Range = Me.Range("B2")
range1.NumberFormat = "0.00%"

This assumes that you add this code to a sheet class in a document-level customization project. If you are using an application-level add-in project, you might use something like the following which formats the cell "B2" in the default sheet of the workbook.

[C#]

Excel.Range range1 = this.Application.get_Range("B2", missing);
range1.NumberFormat = "0.00%";

[VB]

Dim range1 As Excel.Range = Application.Range("B2")
range1.NumberFormat = "0.00%"

I might have found a topic that shows me how to format a cell as a percentage, but sometimes using the macro recorder can be a lot faster. Especially if the task you want to perform is something that can be done by using common Excel features.

You can still search for answers in the docs. The topic Excel Object Model Overview is a great place to start. There is a section in that topic named "Using the Excel Object Model Documentation" that lists several resources.

Norm E.

Peek at Service Pack 1 (Christin Boyd)

VSTO Team — Mon, 12 May 2008 08:42:10 GMT

Visual Studio 2008 Service Pack 1 is not finished yet, but we do have a beta version of the documentation ready for you to read! You can learn about some of the features that you'll see later this year when we release SP1.

I recommend starting with reading about a totally new feature that we put into SP1 that allows you to extend Word documents and Excel Workbooks at runtime from an Application-Level Add-in. Here is the link to the Beta of the documentation:

http://vs2008sp1docs.msdn.microsoft.com/en-us/ms334311.aspx

You'll be able to create objects and respond to events including:

Host Controls
ListObjects
Smart Tags
Word Content Controls
and Events such as DocumentBeforeSave

Only some of the new deployment features have been documented so far. You can read about one of the new deployment features in the Event Logging (2007 System) page in the SP1 documentation here:

http://vs2008sp1docs.msdn.microsoft.com/en-us/ms331997.aspx

Starting in Visual Studio 2008 Service Pack 1 (SP1), you can use the event viewer in Windows to see error messages that are captured by the Visual Studio Tools for Office runtime when you install or uninstall Visual Studio Tools for Office solutions. You can use these messages from the event logger to resolve installation and deployment problems.

The Beta version of the Service Pack is only getting distributed to about a thousand beta testers who have great reputations for submitting clear feedback and bug reports. I hope this little peek at the documentation will get you excited about what's coming later this summer in Service Pack 1.

-Christin Boyd, Program Manager

Databinding best practices for Excel (Christin Boyd)

VSTO Team — Tue, 15 Apr 2008 07:14:00 GMT

I read a question on the forum about databinding in an Excel solution. The developer was asking about Excel 2003, but the answer I wrote will work for both Excel 2003 and Excel 2007. Here's the question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=3122341&SiteID=1&mode=1

As a best practice you can create one dataset in ThisWorkbook designer and then programmatically reference it from your code in other sheets.

Here’s how:

Add new Data Source of Data Base type, by specifying a database connection and selecting tables, views and columns.

Next open ThisWorkbook.vb in the designer. It will look like it's a big gray box with two sentences that say "This is the workbook designer...." Now from the Toolbox, under the Data section, select a DataSet and drag it onto the design surface. When you drop it, you will get a dialog that asks if you want a typed or untyped dataset. Select Typed. It should prepopulate an edit box with <your namespace>.MyDataSet. Click OK. On the design surface you should now see an icon next to MyDataSet1. In C# you will want to set the modifier to Internal or Public on the data set in the property browser.

Next open the code behind ThisWorkbook.vb. Inside the ThisWorkbook_Startup procedure, you should fill your MyDataSet1 instance with code like this:

VB Sample

  DimpatientAdapter As New MyDataSetTableAdapters.PatientsTableAdapter
  patientAdapter.Fill(Me.MyDataSet1.Patients)

  Dim rxAdapter As New MyDataSetTableAdapters.PrescriptionsTableAdapter
  rxAdapter.Fill(Me.MyDataSet1.Prescriptions)

C# sample

  MyDataSetTableAdapters.PatientsTableAdapter ta =
    new MyDataSetTableAdapters.PatientsTableAdapter();
  ta.Fill(myDataSet1.Patients);

Next you can open Sheet1 designer. Now select "Add New Data Source" from the data menu and this time choose to add an "Object" not a database! You will get a dialog that shows the hierarchy and this time DO NOT select the table adapter! Open the name of your project, then the namespace, then you should see MyDataSet. Select it then click OK. This action will create an Object in your Data Sources window.

Now you can select from the Data Sources Window, you should see something called MyDataSet. This object can be used to create a databinding in your sheets. So you can drag from this universal object into any one of your sheets. Grab it and drag it onto Excel Sheet1 and it created an empty table. In order to finish setting it up, select the table and in the property grid click on the arrow next to DataMember property and select the data table that you want to be bound to the table. Try it, and see how it creates a new BindingSource object for each sheet, but you still have just the one DataSet instance.

In each Sheet, you need to add the following line of code for Each table:

Me.PatientsDataTableBindingSource.DataSource = Globals.ThisWorkbook.MyDataSet1

Please let me know through comments on this blog if this explanation works for you. Thank you!

Visual Studio Command Bar for Arranging Controls on Documents and Worksheets (McLean Schofield)

VSTO Team — Fri, 11 Apr 2008 00:05:00 GMT

One of the lesser-known features of Visual Studio Tools for Office is the Microsoft Office Word and Microsoft Office Excel command bar. When you are developing a document-level project for Word or Excel (for example, a Word Document or Excel Workbook project) and you have the document or one of your worksheets open in the designer, this command bar appears in Visual Studio, just above the designer. In Excel, this command bar looks like the following by default.

The first several buttons in this command bar are for changing the keyboard scheme and mapping XML to the document or worksheet. This post is about the purpose of the rest of the buttons.

If you are designing a custom UI for your document or worksheet that includes Windows Forms controls that you add by using the designer, you can use these buttons to arrange the controls with a single click. When you select multiple controls in the designer, these buttons become enabled.

From left to right, here are the buttons you can use:

Align Lefts. This button moves all of the controls to the left, so that they are aligned with the left side of the left-most control.
Align Centers. This button moves all of the controls left or right so that they are aligned around the vertical axis of the widest control.
Align Rights. This button moves all of the controls to the right, so that they are aligned with the right side of the right-most control.
Align Tops. This button moves all of the controls up, so that they are aligned with the top side of the upper-most control.
Align Middles. This button moves all of the controls up or down, so that they are aligned around the horizontal axis of the tallest control.
Align Bottoms. This button moves all of the controls down, so that they are aligned with the bottom side of the bottom-most control.
Make Horizontal Spacing Equal. The left-most and right-most control remain in place; the controls in between move horizontally so that there is equal horizontal space between each control.
Make Vertical Spacing Equal. The top-most and bottom-most control remain in place; the controls in between move vertically so that there is equal vertical space between each control.

A special note about Word. In Word projects, the alignment buttons are enabled only if the selected controls are not in line with text. By default, controls that you add to a Word document at design time are in line with text. To change the layout style of the control, right-click the control and then click Format Control. Then, on the Layout tab, select a wrapping style other than In line with text:

Examples. Enough words! Here are some examples that show these alignment options in action. These examples are pretty contrived, but they should give you an idea of the effects of each option.

Given the following buttons on a worksheet:

Align Lefts rearranges the controls as follows:

Align Centers rearranges the controls as follows:

And Align Rights rearranges the controls as follows:

Given the following buttons on a worksheet:

Align Tops rearranges the controls as follows:

Align Middles rearranges the controls as follows:

And Align Bottoms rearranges the controls as follows:

Given the following buttons on a worksheet:

Make Horizontal Spacing Equal rearranges the controls as follows:

Finally, given the following buttons on a worksheet:

Make Vertical Spacing Equal rearranges the controls as follows:

I hope these options come in handy then next time you are adding controls to a document or worksheet in VSTO.

-------------------------------------------------

McLean Schofield, Programming Writer