Write to an Excel File using WPF

Question

2.33/5 (3 votes)

See more:

Hi Folks,

Have a disturbing doubt, hope mentors at CP would be able to assist.
I have a simple WPF application, in which there is a button.
The button is supposed to write data to an excel sheet, which ain't happening.

I get an error while building the application that:

'Window' is an ambiguous reference between 'Systems.Windows.Window' and 'Microsoft.Office.Interop.Excel.Window'.

Below is my Window1.xaml code:

C#

<Window x:Class="WpfApplication1.Window1"
    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
    Title="Window1" Height="406" Width="345">
    <Grid>
        <Image Margin="12,100,66,12" Name="image1" Stretch="UniformToFill" Source="Images\s3.jpg" />
        <Button Height="23" Margin="0,38,100,0" Name="btnExcel" VerticalAlignment="Top" BorderBrush="Chartreuse" Foreground="DarkMagenta" HorizontalAlignment="Right" Width="75" Click="btnExcel_Click">Excel</Button>
    </Grid>
</Window>

Below is my Window1.xaml.cs code:

C#

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Windows;
using System.Windows.Controls;
using System.Windows.Data;
using System.Windows.Documents;
using System.Windows.Input;
using System.Windows.Media;
using System.Windows.Media.Imaging;
using System.Windows.Navigation;
using System.Windows.Shapes;
using Microsoft.Office.Interop.Excel;
using System.Reflection;

namespace WpfApplication1
{
    /// <summary>
    /// Interaction logic for Window1.xaml
    /// </summary>
    public partial class Window1 : Window
    {
        public Window1()
        {
            InitializeComponent();
        }

        private void btnExcel_Click(object sender, RoutedEventArgs e)
        {
            //creating an excel application
            Microsoft.Office.Interop.Excel.Application excelApp = new Microsoft.Office.Interop.Excel.Application();
            if (excelApp == null)
            {
                MessageBox.Show("Check whether you've added Excel assembly as reference");
            }
            excelApp.Visible = true;

            //creating an object of the workbook
            Workbook wbobj = excelApp.Workbooks.Add(XlWBATemplate.xlWBATWorksheet);

            //adding a worksheet
            Worksheet ws = (Worksheet)wbobj.Worksheets[1];

            //defining the range of the worksheet
            Range sheetRange = ws.get_Range("B1", "B5");

            //creating elements with an array
            int[] array = new int[5];
            for (int i = 0; i < array.Length; i++)
            {
                array[i] = i * 2;
            }
            Object[] obj = new Object[1];
            obj[0] = array;
            sheetRange.GetType().InvokeMember("Value",BindingFlags.SetProperty,null,sheetRange,obj);

        }
    }
}

The above code works perfectly fine when it's done via normal Windows Forms, because the master namespace used is Form. There is no ambiguity here.
Can anybody shed some light on this scenario, as to is it possible to invoke an excel stuff in a WPF application?
Any assistance would be highly appreciated.

Regards
Anurag

Posted 26-Mar-13 7:54am

Anurag Sinha V

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Accepted Answer · 2013-03-26T08:08:00

There are at least three approaches:

Don't write

C#
```
using Systems.Windows.Window;
```
and

C#
```
using Microsoft.Office.Interop.Excel;
```
in the same file. Skip on one of those lines, or both. When a namespace is used, use fully-qualified names, such as

C#
```
Microsoft.Office.Interop.Excel.Window myWindow = //...
```
Excel generation is totally unrelated to WPF. You only export data, never any WPF UI elements. That said, you really should separate Excel generation stuff and WPF code files. Write it all in separate files, and not only because of your problem, but to make your application maintainable.

Use the simple alias syntax:

C#

using Systems.Windows.Window;
// using Microsoft.Office.Interop.Excel // remove, don't use it; instead, use:
using ExcelWindow = Microsoft.Office.Interop.Excel.Window;

//...

ExcelWindow myWindow = //...

What to prefer? In all your practice, you will need to use all of these techniques. As to your particular case, even if you use #1 and #3, you still need to do your best to isolate WPF and Excel parts of the code, so #2 is a must, even if you use the other techniques related to type naming.

—SA