Re: exe giving exception while running on xp - C# Discussion Boards

31-Mar-11 21:48

Hi all,

I have made an application in which i need to save my data in excel sheet, for doing this i have used

using Microsoft.Office.Core;
using Excel = Microsoft.Office.Interop.Excel;

as namespace and its functions..

My problem is my exe run's fine on windows vista and higher version but it is not running on windows xp. When i run it on xp it gives exception.

I am not getting what i am missing in my application.

Thanks in advance

OriginalGriff31-Mar-11 22:27

OriginalGriff

31-Mar-11 22:27

Do you have Excel installed on the XP machine? Is it the right version, or higher?
If not, it won't work...

Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.

Manfred R. Bihy: "Looks as if OP is learning resistant."

situ2131-Mar-11 22:39

31-Mar-11 22:39

yes exel is intalled

Eddy Vluggen31-Mar-11 23:20

Eddy Vluggen

31-Mar-11 23:20

Did you install the correct .NET framework? Did you install the correct Interop DLL's[^]?

I are Troll Suspicious | :suss:

situ2131-Mar-11 23:21

31-Mar-11 23:21

how i install interop

Re: exe giving exception while running on xp [modified]

Eddy Vluggen31-Mar-11 23:27

Eddy Vluggen

31-Mar-11 23:27

satendrasitu wrote:
how i install interop

As described in the link that I posted, that's the reason why it's included Smile | :)

Do read the note at the bottom;

MSDN states;
PIAs are version specific, so you should use the same version of the PIAs as the application version. For example, if you want to migrate your Microsoft Office XP managed code solution to Microsoft Office 2003, you should recompile the Office XP managed code solution with Office 2003 PIAs.

You should also have two different setup packages—one for Office XP and another for Office 2003—if you intend for the same solution to work in both Office XP and Office 2003. Deployment of PIAs for Office XP is very different from that for Office 2003. For further information about these differences, see the ReadMe file included in the Office XP PIAs download[^].

I are Troll Suspicious | :suss:

situ2131-Mar-11 23:34

31-Mar-11 23:34

thanks for this, but how I include this with my exe , because it is not run in client mechine

modified on Friday, April 1, 2011 5:46 AM

Eddy Vluggen1-Apr-11 0:04

Eddy Vluggen

1-Apr-11 0:04

satendrasitu wrote:
thanks for this, but how I include this with my exe

Using a set-up application that installs all required components. Or, you'll have to copy them manually. You can't link them into the executable itself.

..wel, you could add it as an embeddable resource, unpack it and load it on demand, but that would probably cost more than the trouble would be worth.

I are Troll Suspicious | :suss:

Change your Username!!!!

Keith Barrow1-Apr-11 6:44

Keith Barrow

1-Apr-11 6:44

Change your username as soon as possible, otherwise you'll wind up with endless adverts for hair-loss remedies, herbal viagra and pics of nudie ladies and/or gents in your inbox. Unless you want that of course Smile | :)

Sort of a cross between Lawrence of Arabia and Dilbert.[^]
-Or-
A Dead ringer for Kate Winslett[^]

RaviRanjanKr6-Apr-11 19:15

RaviRanjanKr

6-Apr-11 19:15

Actually this type of problem occur due to .net framework missing on the Client System.
to run .net application it required its perquisites. It runs on higher version of XP because .net framework resides implicitly which is not in XP.
so be confirm about it or give us more details what exception is generating while running your application on XP.

LINQ on un-typed IList collections?

Ganesh Kumar Kaki13-Apr-11 2:09

Ganesh Kumar Kaki

13-Apr-11 2:09

which exception it is throwing?

SledgeHammer0131-Mar-11 10:50

31-Mar-11 10:50

Is it possible to use LINQ on an un-typed IList collection? Specifically I'm interested in ListView.SelectedItems. I want to remove every item except item "i".

Not sure how that would work since if I don't know the type, how would I run the query? Although, I'd really only be comparing object o.

Not Active31-Mar-11 11:52

Not Active

31-Mar-11 11:52

It is not untyped, ListView.SelectedItems returns a collection of ListViewItem(s).

I know the language. I've read a book. - _Madmatt

SledgeHammer0131-Mar-11 12:05

31-Mar-11 12:05

Mark Nischalke wrote:

It is not untyped, ListView.SelectedItems returns a collection of
ListViewItem(s).

----

You are mistaken sir Smile | :)

. ListView.SelectedItems most certainly does NOT return ListViewItems (unless you are binding to stock ListViewItems). It returns whatever type you are binding with.

If my ItemsSource is a ObservableCollection<Widget>, SelectedItems returns a collection of Widgets, not ListViewItems.

The definition of ListView.SelectedItems is:

[BindableAttribute(true)]
public IList SelectedItems { get; }

As you can see, un-typed Big Grin | :-D

.

Also, when I look in the debugger, SelectedItems is actually a:

- SelectedItems Count = 1 System.Collections.IList {System.Windows.Controls.SelectedItemCollection}

System.Windows.Controls.SelectedItemCollection is a private class.

Naturally, this fails:

IList<ListViewItem> selectedItems = SelectedItems as IList<ListViewItem>;

because it ain't that type Smile | :)

. Unless you meant something else.

But regardless, as I look in the debugger, <whatever you want to say SelectedItems returned>[0] is NOT a ListViewItem, its a Widget.

My issue is that I don't know what type it is, so I need to do a RemoveAllExceptThis as an object.

Not Active31-Mar-11 12:12

Not Active

31-Mar-11 12:12

I stand corrected. I was thinking of something else

I know the language. I've read a book. - _Madmatt

Keith Barrow31-Mar-11 12:19

Keith Barrow

31-Mar-11 12:19

I don't think so, not directly at least, the standard LINQ operators work on IEnumerable<T>, whereas ListView.SelectedListViewItemCollection only implements IEnumerable. Could be wrong though!

Sort of a cross between Lawrence of Arabia and Dilbert.[^]
-Or-
A Dead ringer for Kate Winslett[^]

SledgeHammer0131-Mar-11 12:53

31-Mar-11 12:53

Yeah, thats what it seems like... Oh well. Thanks anyways.

DaveyM6931-Mar-11 23:51

DaveyM69

31-Mar-11 23:51

It shouldn't be too hard to create your own specialized wrapper version of the collection, perhaps with an explicit conversion operator, that implements IEnumerable<T>

Dave

Binging is like googling, it just feels dirtier.
Please take your VB.NET out of our nice case sensitive forum.
Astonish us. Be exceptional. (Pete O'Hanlon)

BTW, in software, hope and pray is not a viable strategy. (Luc Pattyn)

SledgeHammer011-Apr-11 4:45