FAQ

Why does this site exist?

One of the main aspects of the CLR is to provide a runtime that is language-neutral. That is, it should not matter what language you develop your assemblies in as the CLR is king of the .NET world. However, most .NET developers use C# or VB .NET, and have never spent the time looking at Eiffel or Python. Therefore, I have created this site to provide up-to-date news on the latest in .NET language developments. If a new language is created, or a language has a compiler for the CLR, or an article is published relating to the inner workings of a language, this site keeps you informed via an RSS feed, which you can subscribe to here. Also, I've created a list of essential .NET language resources. There are a lot of solid, thorough resources, both in book and article form, for the .NET developer who has a keen interest in languages and compilers.

Why don't you have language XYZ listed?

Because I may have missed it! Languages pop up here and there, and it's hard to keep track of new developments. If you know of a language that I missed, please let me know!

Why isn't there anything on I/O, or ADO .NET, or (insert related .NET technology here)?

This is a site focused on .NET languages. While site information may touch upon non-language areas when needed (like Remoting, or reflection, or ASP .NET), it's not meant to be a cornucopia of .NET information. There is a wealth of information on .NET on the Internet - just hit your favorite search site (like Google), and start looking.

Can I contribute to the site?

Right now, this is a project run by one person, and I'm trying to get everything done by myself. However, if you'd like to contribute an article to this site, let me know and we'll work on the details.

One thing to keep in mind: any work will be volunteer-based. That is, I can't pay you if you submit material. But I'll give full credit for your work that you want to add to this site that's dedicated to help make the .NET community multi-lingual.