Re: VBA and VSTO
- From: "Niek Otten" <nicolaus@xxxxxxxxx>
- Date: Sat, 1 Apr 2006 22:15:50 +0200
I don't think it is wise to take refuge in a new and unknown tool because the old one causes you problems. I really think you
should try to find out what's wrong with the present application. Only if you find out that there is something that VBA can't do
correctly and VSTO can, you could consider to migrate.
But I don't think that will happen; too many people manage get things right in VBA, albeit with some trouble sometimes.
I don't know what you mean exactly with "I've built a compiler " but it makes me shiver. Don't! Use standard and proven tools
whenever you can!
Just my opinion.....
--
Kind regards,
Niek Otten
"Jos Vens" <jos.vens@xxxxxxxxxxxxxx> wrote in message news:uvxoCCcVGHA.5900@xxxxxxxxxxxxxxxxxxxxxxx
I know,
but if VSTO is stable, I can convince my customers to migrate to 2003, now it's a mess: my excel application crashes on almost
every machine, unless it is upgraded to the right version (like for XP is it 10.6789.6735 SP3). All other versions are crashing,
unless I recompile. I've built a compiler (I use the sendkeys method to unlock the project etc etc... It worked, but on 2003 I
couldn't save it anymore - an error on saving appeared for an unknown reason).
Thanks for all your suggestions!
Jos Vens
"Bob Phillips" <bob.phillips@xxxxxxxxxxxxxxxxxxxx> schreef in bericht news:eIFbDYbVGHA.2444@xxxxxxxxxxxxxxxxxxxxxxx
If you are deploying to Excel 2000 and Xp as well as 2003, VB.Net isn't
really an option anyway.
--
HTH
Bob Phillips
(remove nothere from email address if mailing direct)
"Jos Vens" <jos.vens@xxxxxxxxxxxxxx> wrote in message
news:O1B0EUbVGHA.736@xxxxxxxxxxxxxxxxxxxxxxx
Hi Chip,from
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
vba to vb.net.so
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)
soI 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)
excelI 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
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).
.
- Follow-Ups:
- Re: VBA and VSTO
- From: Jos Vens
- Re: VBA and VSTO
- From: Jos Vens
- Re: VBA and VSTO
- References:
- VBA and VSTO
- From: Jos Vens
- Re: VBA and VSTO
- From: Chip Pearson
- Re: VBA and VSTO
- From: Jos Vens
- Re: VBA and VSTO
- From: Bob Phillips
- Re: VBA and VSTO
- From: Jos Vens
- VBA and VSTO
- Prev by Date: Re: copy and paste
- Next by Date: smoothly linking two presentations
- Previous by thread: Re: VBA and VSTO
- Next by thread: Re: VBA and VSTO
- Index(es):
Relevant Pages
|