Hi everyone,
I am about to upgrade my hardware and software, and would like to know
what I really need to develop and sell Office2010 solutions. Do I need
Visual Studio 2010 or some special developer version of Office or
anything like that?

Most of the development I have done in Office so far is with either 97
or 03. Am I going to be able to reuse most of my code and
methodologies or am I back to step 1. I did a lot of API stuff as well
as some WMI which I am hoping not to have to replace. That being said
I am reasonably comfortable with .Net but don't know if I will need it
for Office development in 2010.

Thoughts and experience greatly appreciated. The more I read the more
confused I get. Looking forward to getting a new toy though!

Cheers

The Frog

On Sun, 7 Aug 2011 04:50:03 -0700 (PDT), The Frog
<mr.frog.to.you (AT) googlemail (DOT) com> wrote:

No. There is a free Access 2007/2010 runtime you can download and
distribute.

Reuse.

Still works.

Mind you not for the web version of Access 2010 which only has macros.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/

Hi Tony,

Thanks for that. Makes life a lot easier indeed! What is VSTO then and
what is it used for - or is this a red herring?
--
Cheers

The Frog

On Mon, 08 Aug 2011 16:45:49 +0200, The Frog
<mr.frog.to.you (AT) googlemail (DOT) com> wrote:

I don't really know. It's been around for a number of
versions/reincarnations but ....

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/

VSTO _used to be_ needed to get the Access Runtime (between the days when
you could buy the "Developer Edition" of Office, and when M'soft provided
the freely downloadable runtime), but it also included VB.NET and C# for
Word and Excel, and some ActiveX controls. Now it has nothing to do with
the runtime, and as far as I know, the groundswell of demand for DotNet
languages for Office was only a figment of Microsoft's imagination (they did
a much better job of selling themselves on the many advantages of 'managed
code' than they did of selling experienced Office developers on those
advantages).

So, if you have a burning desire to code in VB.NET or C# for Word or Excel,
you need VSTO. You cannot use VB.NET or C# with Access, even if you do get
VSTO. I don't know about ActiveX Controls -- most of the experienced Access
developers I hang out with avoid them because they don't want to have to
distribute extra stuff with their Access and the runtime.

--
Larry Linson, Microsoft Office Access MVP
Co-author: "Microsoft Access Small Business Solutions", published by Wiley
Access newsgroup support is alive and well in USENET
comp.databases.ms-access



"Tony Toews" <ttoews (AT) telusplanet (DOT) net> wrote

Thanks for the heads up guys. So if I understand things correctly all I
need to do is to buy a copy of Office 2010 Pro (32 bit) and thats it - I
am good to go. That makes the entire process a lot simpler indeed.

There is one last question regarding office - that of languages. I am a
native english speaker, but I am living in Germany. When I typically buy
software here it comes in the german language. I intend to develop in
the english language, and then just swap the wording on the controls and
menu's etc to produce a german version. Can anyone see an issue with
this in Office 2010? It seems to work fine for me in '97 and '03, but I
have not yet played with 2010.
--
Cheers

The Frog

"Access Developer" <accdevel (AT) gmail (DOT) com> wrote in
news:9ab57mFb44U1 (AT) mid (DOT) individual.net:

I don't really think managed code has anything to do with .NET
integration into Office, since Office is by definition COM, and COM
can't be used in managed code, no?

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

If I remember correctly you have to do a COM wrapper around the managed
code for it to work. Never bothered myself with it actually. I have
found no real need for it with Access. Between windows API and WMI you
can do pretty much anything anyway. Multi-threaded could be nice
though......
--
Cheers

The Frog

"David-W-Fenton" <NoEmail (AT) SeeSignature (DOT) invalid> wrote

VB.NET and C#, as provided in Visual Studio Tools for Office (VSTO), can be
used with Microsoft Word and Microsoft Excel. As far as I know, they
produce 'managed code' just as they do in other cases. I have not had enough
interest to delve any deeper in the subject, because I am not (as you may
know from posts here and elsewhere) a fan, nor proponent, nor user (to any
extent worth mentioning) of DotNet.

I do know there are some software interfaces / connections between .NET and
COM, but I think they may 'work the other way', allowing connection to
DotNet functionality from within a COM application.

--
Larry Linson, Microsoft Office Access MVP
Co-author: "Microsoft Access Small Business Solutions", published by Wiley
Access newsgroup support is alive and well in USENET
comp.databases.ms-access

On Mon, 8 Aug 2011 17:11:27 -0500, "Access Developer"
<accdevel (AT) gmail (DOT) com> wrote:

True enough but I wasn't even thinking of the Access Runtime when I
was thinking of VSTO.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/