Okay, I see all of you points and I raise you one.  I would be happy to extend the core platform but I left my VB behind when I started using .NET ...  For the sole purpose that I found it to have more features "out-of-the-box".  Not really features for ASP.net but I noticed it was getting more attention on the platform side of things at MS.  My friends also told me "I will help you all you want but only if you use C#...".  Being that my friends are people that win awards for their work, I respected their path and chose to use C# as my primary .NET language.  VB.NET is like J# to me, sure it's there and you can use it but you just don't get the same tools and support that C# or C++ do.

I understand that you can add references to libraries written in C# and make a single call to a referenced library with ease but it boils down to branding, marketing, and adoption for me.  Sure I could interop with components and all that good stuff but I really just want to improve the core features like the Blog for example before diving into anything else.

I would definately like to contribute to the project in one way or another and I think I have some projects to offer it but I am just affraid that I will end up programming in VB .NET, which kinda scares me because it's going the complete opposite direction of where I want to go.

You should really checkout code plex but it sounds like you guys had a great solution already using a CI methodology, SVN, and Cruise Control (that's how I roll).  What happened?

Thanks for your insight and patience on this touchy subject.  I look forward to the future ...

Cheers,
T

>Can't you guys just kill the VB.net version and start a new project with C#?

hey my day to day programming languages are assembler and Forth. Lets just cut to the chase and make the thing really hum by rewritting the project in assembler  any offers for Forth? Everyone knows that real programmers don't use High level compilers.

Now a bit more seriously - in what way does DNN actually suck. We are just about finished the customization of 3.3.6 to meet the requirements of our clients it has no real resemblence to version 1 and in fact has not a lot of resemblence to 3.3.6  - what your dnn does is totally bound by your imagination - if your programmers can only think in one language then imagination may not be a major factor.

I do agree with you about the CVS however it would make life a lot easier but then it is not going to happen. I think there is an unoffical C version of DNN some where out there - but boy it would be  bitch to maintain and upgrade to the current releases of DNN

The blog module - there are better blog PA's out there and they are free and some are even written in C. If you don't like the blog then rewrite it,change it, customise it DNN is exactly what you make it

Kosher,  I can see where you're coming from.  Any chance you and your friends can start a new C# conversion of DotNetNuke and make it into an award winning project? 

The fact of the matter is DNN will never be converted to any other language and it is a path chosen by the project owner.  This topic has been raised so many times and at the end of the day DNN will remain written in VB.NET.