Nelak, that's just what I've thought, the Visual Shell SDK isn't
there.
Instead, there is the widely known Visual Studio SDK.
I'm sure that SDK will be of use for you.
You're writing ultimately clear about domain-specific languages.
But it would be a horrible problem if we would have a different
language for every different problem-specific domain.
I just can't imagine myself learning a completely new language, even a
trivial one, every time that I need to solve another problem.
Instead, there are such things like libraries, assemblies, namespaces,
etc, to distinguish the problem-specific domains from each other.
For example, you can be sure that Microsoft.Xna.Framework namespace/
assembly serves the graphics/multimedia domain only, System.Data
serves
ADO.NET and other data only, etc.
It's much better to have only one language to learn and master, with
namespace/assembly sets for every problem-specific domain.
That's why I like .NET :)
Once I finish up reading "Programming C# 3.0", by Jesse Liberty,
Donald Xie (
http://www.oreilly.com/catalog/9780596527433/ ), and some
of MSDN related to .NET, I'll start writing some applications or
assemblies, becouse I've written only just a few 3dsMax plugin classes
so far yet. But I already know that I have a single language to learn,
which is C#, alot of existing assemblies (by Microsoft, MonoProject,
etc), and possibility to create new assemblies, and even the ability
to call COM API from a .NET application.
What language would you want to run with CLR?
What type of end-user applications do you want to have with it?
Actually I don't know what's the current status of Mono.Xna project.
I'll be checking it out when I'm ready to examine the sources.
Anyway, they've done alot of work, though I hope they'll continue
working on it.
Meanwhile, I'm learning, to be capable with helping in future.