Stupid question.

How do I get my hands ionto VSA?

In the past SUmmit was responsible for this, and it was part of VSIP.

Now VSIP is free - Summit still points to VSIP as source, but there is noone
I know of to contact, and on the VSIP download sites I do not find any
reference to VSA.

Can anyone point me in the direction of the correct stuff so that I can get
up to speed and running?

Thanks.

Thomas Tomiczek
THONA Software & Consulting Ltd.
(Microsoft MVP C#/.NET)

Hello, "Thomas Tomiczek [MVP]"
http://www.vsipdev.com

Hi Thomas

I have been trying to find out more about VSA myself, and this is the
response I received from my contact in Microsoft:

"At this time we are not accepting new evaluations for VSA although we will
continue to support customers already in the program. We are evaluating
alternatives for the next version of VSA. In the meantime, we recommend one
of two approaches. If you are looking just for runtime customization and you
don't need an IDE you should use the ICodeCompiler interfaces in the .NET
Framework. If you need an IDE you should investigate integrating into Visual
Studio via the Visual Studio Industry Partner Program
(http://www.vsipdev.com/). We recently announced new levels of VSIP,
including free access to the VSIP SDK. Integrating into Visual Studio via
VSIP offers a more complete solution than VSA, offering WinForms and C#
support for example, neither of which is supplied by VSA. We appreciate your
patience and understanding as we work on our future direction. We look
forward to sharing more information with you as it becomes available".

Hope this helps

Mark


"Thomas Tomiczek [MVP]" <t.tomiczek (AT) thona-consulting (DOT) com> wrote

AH, ok

So basically VSA is history (sort of) and you can not really get your hands
onto it anymore.

Damn.

--
Regards

Thomas Tomiczek
THONA Software & Consulting Ltd.
(Microsoft MVP C#/.NET)
(CTO PowerNodes Ltd.)
---

Still waiting for ObjectSpaces? Tr the EntityBroker today - more versatile,
more powerfull.
And something in use NOW. for the projects you have to deliver - NOW.


"Mark Hammond" <no (AT) spam (DOT) thankyou> wrote

the vsa IDE is history, the vsa runtime support isn't. The only supported
IDE right now is visual studio, but you have to write the addin.

-- bruce (sqlwork.com)



"Thomas Tomiczek [MVP]" <t.tomiczek (AT) thona-consulting (DOT) com> wrote

Ok, so far.

Now, where do I get the RUNTIME from?

How about licensing this one?

--
Regards

Thomas Tomiczek
THONA Software & Consulting Ltd.
(Microsoft MVP C#/.NET)
(CTO PowerNodes Ltd.)
---

Still waiting for ObjectSpaces? Tr the EntityBroker today - more versatile,
more powerfull.
And something in use NOW. for the projects you have to deliver - NOW.


"bruce barker" <nospam_brubar (AT) safeco (DOT) com> wrote

the vsa runtime comes with the standard .net install. See Microsoft.Vsa in
the standard documentation. you are mostly interested in vsasite and
vsaengine. 3 vsaengine's are supplied, javascript.net, vb.net and vsaloader
(an il engine).

when hosting vb.net, you must build a source file on disk for debugging. see
#ExternalSource command. if you google this newsgroup, you should find
sample hosting classes.


-- bruce (sqlwork.com)







"Thomas Tomiczek [MVP]" <t.tomiczek (AT) thona-consulting (DOT) com> wrote

"Thomas Tomiczek [MVP]" <t.tomiczek (AT) thona-consulting (DOT) com> a écrit dans le
message de news: OEb2O4M3DHA.1816 (AT) TK2MSFTNGP12 (DOT) phx.gbl...

As I understood it, VSA's intent was to supercede VBA. And I thought
this included the IDE embedded into applications like Word, Excel and
Outlook. Does this mean that future versions of the applications won't
have an IDE and you'll use VS.Net to extend their functionality?
I personally don't take issue with this approach. I just want to understand
where it's going.

If it does go this way, then they'll be no IDE for the "casual programmer"
who might create macros for himself. Of course, there are very few casual
programmers. Pl. advise. Thanks.

you are correct, but times change.

the current plan for .Net support in Office applications, is to use Visual
Studio for the IDE and debugging. Office still uses VBA for macro support as
Office is still com based.

If office is ever rewritten to be .Net based, then a need for VSA would
reappear.

-- bruce (sqlwork.com)




"hidden" <hidden123456 (AT) hotmail (DOT) com> wrote