Introducing Visual Studio for Applications Beta 2 and Script for the .NET Framework Beta 2 
Author Message
 Introducing Visual Studio for Applications Beta 2 and Script for the .NET Framework Beta 2

Today we released the VSA SDK Beta 2 to the web for folks to try out and
integrate into their applications.  This months scripting clinic is about
Script for the .NET Framework and how to build script into your applications
(if not check out http://www.*-*-*.com/
info - it should be up in a couple of hours)  Script for the .NET Framework
is the .NET equivalent of Windows Script and is built into the .NET
Framework and is fully documented in Beta 2.  VSA builds on Script for the
.NET Framework by providing a great IDE with intellisense, color coding and
debugging for writing scripts to be run in Script for the .NET Framework.
In addition to this there's an extensive SDK that provides a class library
to help with hosting VSA and Script for the .NET Framework in your

http://www.*-*-*.com/

You can download the SDK from
http://www.*-*-*.com/ ;If you have
any questions please feel free to post to microsoft.public.dotnet.vsa - we
monitor that group and will be happy to help with questions etc.  If you are
interested in licensing VSA then please contact Summit Software at

Enjoy

Andrew



Sun, 14 Dec 2003 05:53:08 GMT  
 Introducing Visual Studio for Applications Beta 2 and Script for the .NET Framework Beta 2
Hi,

Our actual application is developed using VC++ 6. In this application, we
use the msscript activex control (msscript.ocx) to provide customization
features through VBScript. I'm busy now doing some research on VS.Net, VSA
and scripting possibilities in the .Net world. The goal of this research is
to see if we can add also VB.Net scripting support to this app (that will
remain developed in VC++6).
I've read the MSDN August article on .Net interop
(http://msdn.microsoft.com/msdnmag/issues/01/08/Interop/Interop.asp). It
explain well how to call .Net objects from a COM application, how to call
COM objects from a .Net application. But we want to achieve something else :
hosting VB.Net scripts in our existing (vc6) application. Do you think this
is possible ? Can you give me advise on how to do it ?

Regards,
Gaetano Di Gregorio.

PS: remove NOSPAM everywhere in my email address to get the real one.


Quote:
> Today we released the VSA SDK Beta 2 to the web for folks to try out and
> integrate into their applications.  This months scripting clinic is about
> Script for the .NET Framework and how to build script into your
applications
> (if not check out http://msdn.microsoft.com/columns/scripting.asp for more
> info - it should be up in a couple of hours)  Script for the .NET
Framework
> is the .NET equivalent of Windows Script and is built into the .NET
> Framework and is fully documented in Beta 2.  VSA builds on Script for the
> .NET Framework by providing a great IDE with intellisense, color coding
and
> debugging for writing scripts to be run in Script for the .NET Framework.
> In addition to this there's an extensive SDK that provides a class library
> to help with hosting VSA and Script for the .NET Framework in your


http://msdn.microsoft.com/library/en-us/dnclinic/html/scripting011620...

- Show quoted text -

Quote:

> You can download the SDK from
> http://www.microsoft.com/downloads/release.asp?ReleaseID=30891  If you
have
> any questions please feel free to post to microsoft.public.dotnet.vsa - we
> monitor that group and will be happy to help with questions etc.  If you
are
> interested in licensing VSA then please contact Summit Software at

> Enjoy

> Andrew



Mon, 15 Dec 2003 18:27:42 GMT  
 Introducing Visual Studio for Applications Beta 2 and Script for the .NET Framework Beta 2
Yes, it is possible and, in fact, pretty easy to do. The VSA engines have
type libraries, for example Microsoft.Vsa.tlb and Microsoft.JScript.tlb. For
the VB.NET runtime engine, you can CoCreate using progid "VsaVbRT" (make
sure you register vsavb7rt.dll first, as it doesn't get registered due to a
bug in the beta2 installer).



Quote:
> Hi,

> Our actual application is developed using VC++ 6. In this application, we
> use the msscript activex control (msscript.ocx) to provide customization
> features through VBScript. I'm busy now doing some research on VS.Net, VSA
> and scripting possibilities in the .Net world. The goal of this research
is
> to see if we can add also VB.Net scripting support to this app (that will
> remain developed in VC++6).
> I've read the MSDN August article on .Net interop
> (http://msdn.microsoft.com/msdnmag/issues/01/08/Interop/Interop.asp). It
> explain well how to call .Net objects from a COM application, how to call
> COM objects from a .Net application. But we want to achieve something else
:
> hosting VB.Net scripts in our existing (vc6) application. Do you think
this
> is possible ? Can you give me advise on how to do it ?

> Regards,
> Gaetano Di Gregorio.

> PS: remove NOSPAM everywhere in my email address to get the real one.



> > Today we released the VSA SDK Beta 2 to the web for folks to try out and
> > integrate into their applications.  This months scripting clinic is
about
> > Script for the .NET Framework and how to build script into your
> applications
> > (if not check out http://msdn.microsoft.com/columns/scripting.asp for
more
> > info - it should be up in a couple of hours)  Script for the .NET
> Framework
> > is the .NET equivalent of Windows Script and is built into the .NET
> > Framework and is fully documented in Beta 2.  VSA builds on Script for
the
> > .NET Framework by providing a great IDE with intellisense, color coding
> and
> > debugging for writing scripts to be run in Script for the .NET
Framework.
> > In addition to this there's an extensive SDK that provides a class
library
> > to help with hosting VSA and Script for the .NET Framework in your


http://msdn.microsoft.com/library/en-us/dnclinic/html/scripting011620...

- Show quoted text -

Quote:

> > You can download the SDK from
> > http://www.microsoft.com/downloads/release.asp?ReleaseID=30891  If you
> have
> > any questions please feel free to post to microsoft.public.dotnet.vsa -
we
> > monitor that group and will be happy to help with questions etc.  If you
> are
> > interested in licensing VSA then please contact Summit Software at

> > Enjoy

> > Andrew



Mon, 15 Dec 2003 22:46:55 GMT  
 Introducing Visual Studio for Applications Beta 2 and Script for the .NET Framework Beta 2


Quote:
> I've read the MSDN August article on .Net interop
> (http://msdn.microsoft.com/msdnmag/issues/01/08/Interop/Interop.asp). It
> explain well how to call .Net objects from a COM application, how to call
> COM objects from a .Net application. But we want to achieve something else
:
> hosting VB.Net scripts in our existing (vc6) application. Do you think
this
> is possible ? Can you give me advise on how to do it ?

Hi,

We do not support calling VSA engines from unmanaged code. You could
potentially try creating your own .NET wrapper object that hosted the
engines, then called that wrapper object from VC++, but this is not a tested
nor a supported scenario, so I would not recommend it.

Peter

--

JScript .NET / VSA Runtime Program Manager
Please post all questions to the group. Thanks.



Mon, 15 Dec 2003 23:01:08 GMT  
 
 [ 4 post ] 

 Relevant Pages 

1. Visual Studio .Net 2003 Final Beta, simple socket code breaks between 2002 and 2003

2. Any sample code that works with Visual Studio.net Beta 2

3. Visual Studio .NET Beta 2 Service Pack 2 fixes time limitation

4. Visual Studio.NET Beta 1 (English)

5. Visual Studio 6 and Visual Studio .NET

6. Visual Studio 6.0, Visual Studio.Net Difference

7. Visual Studio 6 and Visual Studio .net

8. Visual Studio.NET vs Visual Basic.NET

9. Visual Studio .NET freezes when trying to run an application

10. WinXP-Visual Studio 6.0-Studio.Net compatibility

11. WinXP-Visual Studio 6.0-Studio.Net compatibility

12. VB.NET vs. Visual Studio.NET

 

 
Powered by phpBB® Forum Software