Sign up ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free.

Our C++ MFC application gives the user the ability to define custom scripts in vbscript (via the VBScript engine).

Since (parts of) the application are moving to .NET anyway, and since vbscript seems to be a legacy technology, we are thinking about adding a new scripting component where the user can add his scripts as VB.NET.

Arguments for VB.NET are:

  • Users already are "used to" the syntax
  • Automatic conversion from vscript scripts to VB.NET scripts will be easier due to syntactic similarities

What other arguments pro (or con) VB.NET as a in-application scripting language are there?

Note that the users writing these scripts are not programmers by trade, so any alternative has to take that into consideration.

share|improve this question

closed as not a real question by thorsten müller, gnat, GlenH7, Martijn Pieters, Bart van Ingen Schenau May 17 '13 at 16:46

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

possible duplicate of VB.Net vs C# debate – gnat May 17 '13 at 9:22
Visual Basic .NET isn't a scripting language. – Ramhound May 17 '13 at 12:22
What research have you performed? What indications have you seen that such a migration is a bad (or good) idea? Is your question focusing on the end users being able to adjust to VB.Net or is it about impacts to the existing scripts that you're concerned about? – GlenH7 May 17 '13 at 13:16
certainly has to run through a compiler which produces intermediate code (just like other .net languages). So if you can use something that can read this code then you should be ok. But I don't know if such a thing exists. But make no mistake, your users won't be able to just fire up Notepad and write stuff. – PeteH May 17 '13 at 13:38

1 Answer 1

up vote 3 down vote accepted

One of the big advantages of the .NET framework is that if your app exposes a .NET CLI (Common Language Interface, not Command Line Interface) you can use any of the family of .NET/CLI languages for scripting, including VB.NET, C++/CLI, C#, F#, probably IronPython, etc.

That means you can defer the choice to your users, and use VB.NET as an easier conversion target from your old vbscripts where you need it.

share|improve this answer
+1. That's the point of a Common Language Infrastructure. – Jörg W Mittag May 17 '13 at 13:19

Not the answer you're looking for? Browse other questions tagged or ask your own question.