D
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.
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.