Hi Martin,
Thanks for your explanation.

Probably a cleaner approach to these enhancements would be to just create namespaces for them and have standard and similar constructs ( if really necessary) in both languages to access/use them ( dont pollute the language just to make a feature easier to use in one vs the other).

As far as VB and the approach, whats trendy today may be obsolete tomorrow, so I would not bend the language to suit a certain trend.
IDE tools, and as you said, helpers, as blocks/api/classes could do just that.

I guess java is still a good example to follow in terms of keeping the language isolated of features/packages/constructs.


Regards,
Vlad


>They don't have different roadmaps, but differents approaches to some >issues, while both will keep the same level of management over the .NET >framework.
>
>The C# team wants to keep the language isolated from external influences >and technologies, even if that needs the developer has something to do by >hand (in most cases once and for all).
>
>The VB team has a more pragmatic approach where hey may tie the language to >something that they see today as universal, as in the case of XML. They are >letting you handle XML literals within the language as if they were part of >the code. C# won't have that, although you can do exactly the same in code.
>
>Also, the IDEs can start presenting specific helpers that are different in >both. Nothing to worry about.
>
>Regards,