Re: VBA and VSTO

Tech-Archive recommends: Fix windows errors by optimizing your registry

You'll find the syntax of VB.NET familiar if you know VBA, but
VB.NET is vastly larger and more complicated than VBA. Some code
will copy/paste, but most will require some degree of rewrite.


--
Cordially,
Chip Pearson
Microsoft MVP - Excel
Pearson Software Consulting, LLC
www.cpearson.com




"Jos Vens" <jos.vens@xxxxxxxxxxxxxx> wrote in message
news:O1B0EUbVGHA.736@xxxxxxxxxxxxxxxxxxxxxxx
Hi Chip,

I mean, I developped in VBA, and I don't want to spend to much
time to set my code in vb.net. Is the language comparable or do
I have to learn a lot (and debug a lot) to get my code back in
vb?

I never used VB.NET! I assume you mean I cannot copy and paste
my code from vba to vb.net.

Jos

"Chip Pearson" <chip@xxxxxxxxxxxx> schreef in bericht
news:uuJmpPYVGHA.1728@xxxxxxxxxxxxxxxxxxxxxxx
Assuming you know VB.NET,

1. Is my code in VBA in a high level portable to the new
platform

Only you can answer that question.

2. Can I compile the project to an executable stand-alone
file (.exe) so I am not dependent to what the user have
installed of dll's

With VTSO, you end up with a workbook and a managed code DLL.

3. Does it work with all versions of Office (starting with
2000)

No. 2003 only.


--
Cordially,
Chip Pearson
Microsoft MVP - Excel
Pearson Software Consulting, LLC
www.cpearson.com



"Jos Vens" <jos.vens@xxxxxxxxxxxxxx> wrote in message
news:ubE1QEYVGHA.5020@xxxxxxxxxxxxxxxxxxxxxxx
Hi,

since I have serious problems in VBA, I consider to migrate
to VSTO. I have some questions about that, in order of
importance:

1. Is my code in VBA in a high level portable to the new
platform
2. Can I compile the project to an executable stand-alone
file (.exe) so I am not dependent to what the user have
installed of dll's
3. Does it work with all versions of Office (starting with
2000)

Thanks for your help.
Jos Vens

PS my big problem in VBA is the difference of the mso.dll
(mso9.dll for office 2000) of the different office versions,
which causes a crash on startup when I build up my menu-bar.
Recompilation on the specific excel version solves the
problem, but then I have to maintain at least 3 versions
(2000, XP and 2003). Even subversions (Service Packs and
minor upgrades cause those commilation problems so I cannot
keep that much versions).







.

Relevant Pages

  • Re: VBA errors in 2007 (works fine in 2003)
    ... It's just breaking on the Mac version of Excel. ... Pak allowing you to call functions in the ATP from within VBA. ... menu in VBA, choose References, and select "atpvbaen.xls". ... If there is the possibility of a name collision (two or more libraries ...
    (microsoft.public.excel.misc)
  • Re: VBA errors in 2007 (works fine in 2003)
    ... The file is working as intended now in Excel 2003 and 2007. ... Pak allowing you to call functions in the ATP from within VBA. ... menu in VBA, choose References, and select "atpvbaen.xls". ... If there is the possibility of a name collision (two or more libraries ...
    (microsoft.public.excel.misc)
  • Re: VBA and VSTO
    ... so I am not dependent to what the user have installed of ... Is my code in VBA in a high level portable to the new ...
    (microsoft.public.excel.programming)
  • Re: DLL Vs. EXE?
    ... Whilst it could interact with VBA in a workbook I kind of doubt ... A VBActiveX DLL is activated via a Public class, ... this is instanciated when Excel starts. ... DLL (vs EXE). ...
    (microsoft.public.excel.programming)
  • Re: Working example how to create a DLL using Visual C# 2008
    ... This compiled fine and runs OK in both Excel 2007 and 2003 ... Tolls References or Tools Add-ins so that I can use it from within the Excel ... > meaningful VBA projects. ... >>language hasn't been updated in nearly a decade. ...
    (microsoft.public.excel.programming)