By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
444,041 Members | 958 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 444,041 IT Pros & Developers. It's quick & easy.

Dependencies

P: n/a
Art
Forgive this cross posting -- I may have posted this originally in the wrong
spot -- also I do have a little more information.

I've put together an application that runs on my machine -- the one I
developed it on. I've deployed it on the user's machine, and most of it
works as expected.

One of the things the application does is to open an Excel file and display
a sheet. On my machine this works. On the user's machine I get a .net
exception. I can list all of the stuff in the details window if that would
be helpful. What I'm hoping is that there was something I needed to set when
I build the application for the deployement.

I do recall when I first built it, getting a warning about dependencies. I
downloaded depends.exe, but have no clue how to use it, or what to do if it
reports something.

Any suggestions?

Art

Nov 21 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
* =?Utf-8?B?QXJ0?= <Ar*@discussions.microsoft.com> scripsit:
One of the things the application does is to open an Excel file and display
a sheet. On my machine this works. On the user's machine I get a .net
exception. I can list all of the stuff in the details window if that would
be helpful. What I'm hoping is that there was something I needed to set when
I build the application for the deployement.


What exception? Are you sure the same version of Office you used for
development is installed on the user's PC?

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>
Nov 21 '05 #2

P: n/a
Art
Herfried,

I just checked. I developed it using Office 2002. The user's machine has
Office 2000. I'm going to upgrade the users machine -- we're in the process
of doing that anyway, so I'll just get her upgraded sooner. Hopefully that's
the problem.

As I said I'm currently using Office 2002, but we're upgrading to 2003. If
I take my application (developed using 2002) and put it on a machine with
2003, should it work? Really the only area with the problem seems to be
opening the Excel worksheet -- I guess this is the "com" stuff.

Art
Nov 21 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.