called uncompiled scripts from compiled code...

[Daniel Bass]

For some bespoke software, my client has stated that they'd like their
engineer guys to be able to configure, and muck around with the program we
give them. I don't like it, but what I think about it, does't really matter.

What are the ways to expose the code to them, so that they can change it on
the fly, and there's no need to have VS.Net or the .Net SDK installed
(unless parts of sdk are freely and easily redistributable).

- Is there a way I can call scripts from .Net... One way I thought was to
call into a .VBS file (or the like) and let that go off and perform a load
of functions and tasks etc, returning a value back when it's done.
- Another way I thought was to have the csc.exe at hand, and compile my
libraries at runtime, so that the source for some DLL's is lying around
ready to be edited, and when they are change, the code will recompile them
into the DLL's it's calling.

Perhaps there's a .Net way for doing all this?

Thanks for your time and feedback.

Dan.

[Vadym Stetsyak]

Look in Microsoft.Vsa namespace, particulary IVsaEngine, IVsaSite.

using this you will be able to compile scripts that use already instantiated
objects. Then you can use them using JScript
"Daniel Bass" <I'm really @ sick of spam> wrote in message
news:ep**************@tk2msftngp13.phx.gbl...

For some bespoke software, my client has stated that they'd like their
engineer guys to be able to configure, and muck around with the program we
give them. I don't like it, but what I think about it, does't really matter.
What are the ways to expose the code to them, so that they can change it on the fly, and there's no need to have VS.Net or the .Net SDK installed
(unless parts of sdk are freely and easily redistributable).

- Is there a way I can call scripts from .Net... One way I thought was to
call into a .VBS file (or the like) and let that go off and perform a load
of functions and tasks etc, returning a value back when it's done.
- Another way I thought was to have the csc.exe at hand, and compile my
libraries at runtime, so that the source for some DLL's is lying around
ready to be edited, and when they are change, the code will recompile them
into the DLL's it's calling.

Perhaps there's a .Net way for doing all this?

Thanks for your time and feedback.

Dan.

[Daniel Bass]

Cheers, I'll look into it.

Dan.

"Vadym Stetsyak" <pd****@ukr.net> wrote in message
news:un**************@TK2MSFTNGP11.phx.gbl...
Look in Microsoft.Vsa namespace, particulary IVsaEngine, IVsaSite.

using this you will be able to compile scripts that use already instantiated
objects. Then you can use them using JScript
"Daniel Bass" <I'm really @ sick of spam> wrote in message
news:ep**************@tk2msftngp13.phx.gbl...

For some bespoke software, my client has stated that they'd like their
engineer guys to be able to configure, and muck around with the program we
give them. I don't like it, but what I think about it, does't really matter.
What are the ways to expose the code to them, so that they can change it on the fly, and there's no need to have VS.Net or the .Net SDK installed
(unless parts of sdk are freely and easily redistributable).

- Is there a way I can call scripts from .Net... One way I thought was to
call into a .VBS file (or the like) and let that go off and perform a load
of functions and tasks etc, returning a value back when it's done.
- Another way I thought was to have the csc.exe at hand, and compile my
libraries at runtime, so that the source for some DLL's is lying around
ready to be edited, and when they are change, the code will recompile them
into the DLL's it's calling.

Perhaps there's a .Net way for doing all this?

Thanks for your time and feedback.

Dan.