Add scripting/VBA/.NET to existing windows application.

[Guest]

I have a mature C/C++ application to which I am wanting to add custom
delevopment/scripting capabilities. Initially this will be used as part of a
testing framework.

It appears to me that VBA has been replaced with the .NET environment, and I
am interested in what tools are available for creating such a development
environment (eg generating a custom IDE) and a list of the basic interfaces
that the existing app would need to support to be a .NET server (?is my
terminology right?).

Firstly, is .NET the only real solution to my scripting requirement - or
other things available? Ideally I only require an in process solution.

I would greatly appreciate it if I could be provided with some links/book
references of information that would help get me up to speed on the
terminology/requirements here.

Please note I am looking at this in terms of exporting to the .NET
environment, not actually using it myself! I also believe that it will very
difficult to remove the application from it's own process space, hence I
would prefer solutions that can run 'in proc' and/or include a ready formed
interprocess communication framework.

Thanks,

Hugh Dixon

 

[clintonG]

I too would like to get started learning how to use the .NET Framework
to offer an API that I could make available to customers using the
applications I am working on.

 

[Cor Ligthert]

Darren,

The answer can be short, VBA has not been replaced by the .Net environment
in the same way as JScript has not been replaced by Java.

Cor

 

[Cor Ligthert]

....Correction

I always thread VBA the same as VBS.

I think that this link can help you

http://msdn.microsoft.com/office/understanding/vsto/default.aspx

Cor

 

[Phil Wilson]

Take a look at this, it's JScript but the same principles apply:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnclinic/html/scripting06112001.asp

I did an article for WDJ, March 2003;
http://www.wdj.com/wdm/articles/2003/0303/ registration required

I think maybe the VSAEngine isn't encouraged any more, so CodeDOM could be a
useful alternative.
http://support.microsoft.com/default.aspx?scid=kb;en-us;821778

 

[clintonG]

Thanks Phil -- that was good stuff.


--
<%= Clinton Gallagher, "Twice the Results -- Half the Cost"
Architectural & e-Business Consulting -- Software Development
NET (e-mail address removed)
URL http://www.metromilwaukee.com/clintongallagher/

Take a look at this, it's JScript but the same principles apply:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnclinic/html/scripting06112001.asp

I did an article for WDJ, March 2003;
http://www.wdj.com/wdm/articles/2003/0303/ registration required

I think maybe the VSAEngine isn't encouraged any more, so CodeDOM could be a
useful alternative.
http://support.microsoft.com/default.aspx?scid=kb;en-us;821778
--
Phil Wilson
[MVP Windows Installer]
Definitive Guide to Windows Installer
http://www.amazon.com/exec/obidos/tg/detail/-/1590592972/104-7044380-4696760

I have a mature C/C++ application to which I am wanting to add custom
delevopment/scripting capabilities. Initially this will be used as part
of a
testing framework.

It appears to me that VBA has been replaced with the .NET environment, and
I
am interested in what tools are available for creating such a
development
environment (eg generating a custom IDE) and a list of the basic
interfaces
that the existing app would need to support to be a .NET server (?is my
terminology right?).

Firstly, is .NET the only real solution to my scripting requirement - or
other things available? Ideally I only require an in process solution.

I would greatly appreciate it if I could be provided with some
links/book
references of information that would help get me up to speed on the
terminology/requirements here.

Please note I am looking at this in terms of exporting to the .NET
environment, not actually using it myself! I also believe that it will
very
difficult to remove the application from it's own process space, hence I
would prefer solutions that can run 'in proc' and/or include a ready
formed
interprocess communication framework.

Thanks,

Hugh Dixon

 

[Guest]

Thanks for all the info. I am currently looking through Phil's links, and
believe I will be able to get an idea of what's involved (VB presents me with
a 'learning challenge', but I'm getting there...)

Thanks again for all the thoughts/ideas etc.


Hugh