I work for a large company, and we are using Microsoft Visual Studio
8.

A large c++ library of EXCEL tools was placed on the network drive.

I then copied all the files to my own local C drive to work on my own
version.

However, it doesn't build the xll correctly.

My local version does build and compile without errors.

I then run it in debug mode and it correctly fires up EXCEL.

However, where it goes wrong is that it never builds the file fred.xll

(The name "fred" is a fictitious name, that I'm using for
confidentiality reasons.)


I would very much appreciate help. I can also be contacted at
pauldepstein at yahoo dot com

I'm aware that there are dozens of websites which show you how to load
and build xll files. However, this is different -- I'm not building
an xll from scratch.

When I try and set breakpoints to debug the c++, I get messages saying
that the breakpoints won't be hit because symbols haven't been loaded
for the document. I believe, after talking to colleagues, that the
problem is with building the xll.

Paul Epstein

On Aug 10, 3:35 pm, wrote:
I work for a large company, and we are using Microsoft Visual Studio
8.

A large c++ library of EXCEL tools was placed on the network drive.

I then copied all the files to my own local C drive to work on my own
version.

However, it doesn't build the xll correctly.

My local version does build and compile without errors.

I then run it in debug mode and it correctly fires up EXCEL.

However, where it goes wrong is that it never builds the file fred.xll

(The name "fred" is a fictitious name, that I'm using for
confidentiality reasons.)

I would very much appreciate help. I can also be contacted at
pauldepstein at yahoo dot com

I'm aware that there are dozens of websites which show you how to load
and build xll files. However, this is different -- I'm not building
an xll from scratch.

When I try and set breakpoints to debug the c++, I get messages saying
that the breakpoints won't be hit because symbols haven't been loaded
for the document. I believe, after talking to colleagues, that the
problem is with building the xll.

Paul Epstein

I managed to solve my own problem.

I needed to type "$(TargetPath)" into the right section of the
configuration manager.

Anyway, I'm clearly a newbie to visual c++ excel development, so
advice on books and websites would be welcome.

I have excel add-in development in c/c++ by Steve Dalton which is
excellent -- it just doesn't assume the set-up of working with a c/c++
library.

Paul Epstein