I just learned about the "Office Developer" described in the following MS
article:

http://support.microsoft.com/kb/306130/EN-US

1) How can I find out if it is installed on my machine?

2) How can I learn more about this?

3) Is it a good tool to use for developing Add-in's or should I not bother
(I'm new to Add-ins, but not coding, I would like to explore possibility of
add-ins)?

Thanks much in advance for your assistance.

#1 You'd have installed it. :)

#2 The development methods in Office Developer are essentially the same as
writing macros, so if you're used to what can be achieved there then you'll
have a good idea of it's capabilities within each of the office applications.
The main thing is that you can compile your code to redistribute it. I'm
sure others can chime in with the myriad of things I've missed.

#3 It depends on who your customers are - personally I'd use Visual Studio
with VSTO for developing new content. Certainly long-term you're going to be
better off with that instead.


"XP" wrote:

I just learned about the "Office Developer" described in the following MS
article:

http://support.microsoft.com/kb/306130/EN-US

1) How can I find out if it is installed on my machine?

2) How can I learn more about this?

3) Is it a good tool to use for developing Add-in's or should I not bother
(I'm new to Add-ins, but not coding, I would like to explore possibility of
add-ins)?

Thanks much in advance for your assistance.

#1 You'd have installed it. :)

Yes and you'd best be able to check for that by looking for "New Project" on
the File menu in the VBE. If it's not there you don't have the developer
version installed. You're not likely to have it installed without knowing
it though. It's not cheap for one thing.

The main thing is that you can compile your code to redistribute it

Your code is definitely more secure if that's an issue. Also the com
add-in's code runs in its own 'address space'. This is real nice for VBE
add-ins since you call run your add-in when you're running/debugging your
normal code. E.g., http://www.rondebruin.nl/vbebookmarks.htm

Office 2002 may have been the last version with a developer version. I'm
not sure if Office 2003 had one but Office 2007 didn't. So it's 'old
technology' at this point, like VB6. That doesn't mean it's not useful and
good, etc. Just that things have moved on the .NET and VSTO.

--
Jim
"James Snell" wrote in message
...
| #1 You'd have installed it. :)
|
| #2 The development methods in Office Developer are essentially the same as
| writing macros, so if you're used to what can be achieved there then
you'll
| have a good idea of it's capabilities within each of the office
applications.
| The main thing is that you can compile your code to redistribute it. I'm
| sure others can chime in with the myriad of things I've missed.
|
| #3 It depends on who your customers are - personally I'd use Visual Studio
| with VSTO for developing new content. Certainly long-term you're going to
be
| better off with that instead.
|
|
| "XP" wrote:
|
| I just learned about the "Office Developer" described in the following
MS
| article:
|
| http://support.microsoft.com/kb/306130/EN-US
|
| 1) How can I find out if it is installed on my machine?
|
| 2) How can I learn more about this?
|
| 3) Is it a good tool to use for developing Add-in's or should I not
bother
| (I'm new to Add-ins, but not coding, I would like to explore possibility
of
| add-ins)?
|
| Thanks much in advance for your assistance.

Anyone know if there is a VSTO-lite that's free (and worth anything)?

We are in the midst of budget cuts...

"Jim Rech" wrote:

#1 You'd have installed it. :)

Yes and you'd best be able to check for that by looking for "New Project" on
the File menu in the VBE. If it's not there you don't have the developer
version installed. You're not likely to have it installed without knowing
it though. It's not cheap for one thing.

The main thing is that you can compile your code to redistribute it

Your code is definitely more secure if that's an issue. Also the com
add-in's code runs in its own 'address space'. This is real nice for VBE
add-ins since you call run your add-in when you're running/debugging your
normal code. E.g., http://www.rondebruin.nl/vbebookmarks.htm

Office 2002 may have been the last version with a developer version. I'm
not sure if Office 2003 had one but Office 2007 didn't. So it's 'old
technology' at this point, like VB6. That doesn't mean it's not useful and
good, etc. Just that things have moved on the .NET and VSTO.

--
Jim
"James Snell" wrote in message
...
| #1 You'd have installed it. :)
|
| #2 The development methods in Office Developer are essentially the same as
| writing macros, so if you're used to what can be achieved there then
you'll
| have a good idea of it's capabilities within each of the office
applications.
| The main thing is that you can compile your code to redistribute it. I'm
| sure others can chime in with the myriad of things I've missed.
|
| #3 It depends on who your customers are - personally I'd use Visual Studio
| with VSTO for developing new content. Certainly long-term you're going to
be
| better off with that instead.
|
|
| "XP" wrote:
|
| I just learned about the "Office Developer" described in the following
MS
| article:
|
| http://support.microsoft.com/kb/306130/EN-US
|
| 1) How can I find out if it is installed on my machine?
|
| 2) How can I learn more about this?
|
| 3) Is it a good tool to use for developing Add-in's or should I not
bother
| (I'm new to Add-ins, but not coding, I would like to explore possibility
of
| add-ins)?
|
| Thanks much in advance for your assistance.

Actually, I'm on a work machine loaded by IT so I didn't install Office at all.

Thanks for your reply.

"James Snell" wrote:

#1 You'd have installed it. :)

#2 The development methods in Office Developer are essentially the same as
writing macros, so if you're used to what can be achieved there then you'll
have a good idea of it's capabilities within each of the office applications.
The main thing is that you can compile your code to redistribute it. I'm
sure others can chime in with the myriad of things I've missed.

#3 It depends on who your customers are - personally I'd use Visual Studio
with VSTO for developing new content. Certainly long-term you're going to be
better off with that instead.


"XP" wrote:

I just learned about the "Office Developer" described in the following MS
article:

http://support.microsoft.com/kb/306130/EN-US

1) How can I find out if it is installed on my machine?

2) How can I learn more about this?

3) Is it a good tool to use for developing Add-in's or should I not bother
(I'm new to Add-ins, but not coding, I would like to explore possibility of
add-ins)?

Thanks much in advance for your assistance.