Consider looking for related projects for help or ask at the Teahouse. If you are not currently a project participant and wish to help you may still participate in the project. This status should be changed if collaborative activity resumes.
Some Wikipedians have formed a project to better organize information in articles related to Microsoft's .NET Framework. This page and its subpages contain their suggestions; it is hoped that this project will help to focus the efforts of other Wikipedians. If you would like to help, please inquire on the talk page and see the to-do list there.
Similar to the Collaboration of the week, but on a smaller scale, you might want to "adopt" an article. This would involve doing the research, writing, and picture-taking (if possible) for either a non-existent article or a stub. Of course, everyone else can still edit an adopted article, and you can work on other things too, but the idea is to find a focus for a while, to try and build up the number of quality articles the Project has produced.
This article is within the scope of WikiProject Microsoft, a collaborative effort to improve the coverage of articles relating to Microsoft on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.MicrosoftWikipedia:WikiProject MicrosoftTemplate:WikiProject MicrosoftMicrosoft articles
Please feel free to list your new .NET-related articles here (newer articles at the top, please). Any new articles that have an interesting or unusual fact in them should be suggested for the Did you know? box on the Main Wikipedia page. DYK has a 72 hr. time limit from the creation of the article.
I have used both these languages extensively since .NET emerged and I don't really find too much to complain of in the linked article. In fact, I think it's a pretty good comparison, better than I see most places on the web. The one thing I would add would be a discussion of the Windows Designer added to C#, which makes it competitive with VB for rapid development. I might also add a mention of the fact that VB has nearly twice as many keywords as C#, which probably says something about the two languages but I'm not sure what--that VB takes longer to learn all of it? That it provides some extra help for some things? Anyway, would you mind clarifying why you consider the article biased? Or has it been cleaned up already?