Current status of scripting in .NET

Hi there,
First let me define the problem: I have a .NET application, which is a
fairly big one. There are parts of it that I'd like to expose through
a scripting solution so that 3rd parties can extend the functionality.
However, I also have to find a way to allow them to build their own
GUIS.
for the last couple of hours, I have been looking at various
resources, and it seems that there is not much action in the .NET
world in the scripting field. Actually, most of the resources about
scripting goes back to 2001.
For .NET 2.0, what are the options/technologies for scripting? VSA
seems to be going away, but what is going to replace it? What kind of
best practices are offered by Microsoft for scripting?

Cheers
Seref Arikan

<serefarikan (AT) gmail (DOT) com> wrote

Hi there,
First let me define the problem: I have a .NET application, which is a
fairly big one. There are parts of it that I'd like to expose through
a scripting solution so that 3rd parties can extend the functionality.
However, I also have to find a way to allow them to build their own
GUIS.
for the last couple of hours, I have been looking at various
resources, and it seems that there is not much action in the .NET
world in the scripting field. Actually, most of the resources about
scripting goes back to 2001.
For .NET 2.0, what are the options/technologies for scripting? VSA
seems to be going away, but what is going to replace it? What kind of
best practices are offered by Microsoft for scripting?

PowerShell is the future of scripting. The management interface for
Exchange 2007 was all done with PowerShell, the GUI (MMC) management
interface was then built on top of that.

It's easy to execute PowerShell scripts from your .NET app and it's easy to
expose your app via PowerShell cmdlets and/or a PowerShell provider.

See http://www.microsoft.com/PowerShell to get started.

Hi John,
Thanks for the answer. PowerShell seems to be positioned towards
administrative functions, though I've seen examples of it used to
extend GUI apps. Will check it out

Regards
Seref Arikan

On Sep 24, 10:21 pm, "John Vottero" <JVott... (AT) mvpsi (DOT) com> wrote:

serefari... (AT) gmail (DOT) com> wrote in message

news:1190373132.506701.167130 (AT) 22g2000hsm (DOT) googlegroups.com...

Hi there,
First let me define the problem: I have a .NET application, which is a
fairly big one. There are parts of it that I'd like to expose through
a scripting solution so that 3rd parties can extend the functionality.
However, I also have to find a way to allow them to build their own
GUIS.
for the last couple of hours, I have been looking at various
resources, and it seems that there is not much action in the .NET
world in the scripting field. Actually, most of the resources about
scripting goes back to 2001.
For .NET 2.0, what are the options/technologies for scripting? VSA
seems to be going away, but what is going to replace it? What kind of
best practices are offered by Microsoft for scripting?

PowerShell is the future of scripting. The management interface for
Exchange 2007 was all done with PowerShell, the GUI (MMC) management
interface was then built on top of that.

It's easy to execute PowerShell scripts from your .NET app and it's easy to
expose your app via PowerShell cmdlets and/or a PowerShell provider.

Seehttp://www.microsoft.com/PowerShellto get started.