Where is DNN getting its development methodology from?  There are so many opensource platforms out there for source control, issue tracking etc., yet DNN's only option is to download a zip file of the source?

Why isn't there a repository on codeplex, subversion, or CVS where developers can simply checkout the solution and compile it?

Why VB.net?  There is much more support out there with C# for things like interop, windows presentation foundation, and many other development tools related to C# and not VB.net!  VB.net just got documentation for christ's sake... Can't you guys just kill the VB.net version and start a new project with C#?

This project has so much potential but it seems stifled by all of these non-standard practices.  It's fraught with errors and hasn't changed much since version 1.0.  The community is starving for a solution like this and DNN is the only option for .NET but it lacks so many basic features found in other platforms like Drupal or TypePad, which are sadly written in PHP.  The BLOG module is a far cry from other solutions available in other languages, the feedback module is practically useless, and the best I've yet to build is a simple site with a forum and a nice skin.  Anything more requires that you actually get the solution to compile on your local machine, which is an endless uphill battle in itself.

I'm no noob here but I sure feel like I am stepping into a tangled web of issues.  Ever heard the term KISS?

It's about time for this project to start thinking outside the box.

</Gripe>

I have used source gear vault and it works but it's lacking the features that CodePlex, a free source repository, has built in.  Issue tracking, tasks, and integration with VS.net are all free with CodePlex.  And the fact that it's part of the Web makes it perfect for a project like this one.

I never said to scrap the base application logic, code base, or any of that... I just said kill the VB.net version.  I think there are quite a few more developers, at least that I know, that develop in C#.  Coming from the basic web application, sure you can do everything in VB.net that you can in C#.  But being that I come from a rich development background I look for more features like Native language Interop (C++ interop) to leverage libraries written by very talented developers out there, a feature not provided by VB.net.  I look for other platform tools not available in VB.net, such as Windows Presentation Foundation, XAML, and I believe Windows Presentation Foundation Everywhere.  That's just too big a picture for you guys to see, I think.  I don't know though...

I understand that the application is easily extended and allows developers to create modules with very little effort but I am just griping because there is so much room for improvement here.  I totally respect Sean's ability to execute on his vision but being that this is an open source project, and I know I am not the only one griping here, some of the features and things I am talking about should absolutely be open for discussion and not blindly (close mindedly) shot down in the dark.

You might be wondering who I am and what I have done to merit such a pompis attitude, which I understand.  To you I am yet another developer spilling his woes on a forum and no one worth paying any reasearch time to.  But step out of your role for a minute and try to look at the big picture and where Microsoft is going with its technology.  It's not just about a simple website anymore.

Okay?  Okay!

Peace,
T

Couple of things about the source setup, since its not open to the public does it really matter what is used? I agree that there should be a series of items to have a solid dev foundation but I don't think Codeflex is the all answer either. We are in the middle of changing gears a bit w/ modules making the 1.1 to 2.0 transition, but in the past we have used Draconet, nant, subversion and vault all together to have a CI process in place. With 2.0 you can tie nant to use msbuild and run the same CI process only slightly modified. At work we use subversion and the tortoise client, but still use all the other tools outside of vault and it has worked wonderfully.

Here is a fact, the VB.NET version will not be killed. Over the past several years Shaun has also stated a C# version IS NOT coming either. It is ridiculous to maintain multiple languages of the same application when it is constantly evolving such as this one. I seriously doubt that the team is not seeing the big picture, you can use all those tools you mentioned you just need to know how to do it (not doubting your level, just not sure you are thinking how to accomplish it in a manner that will work w/ DNN).

I am all for you talking about the future and I don't think I am very close minded. I work w/ c++, c#, vb.net, the language is irrelevant to me. I too, however, have to respect the decisions which have been made and I am also here to communicate that some of these issues (such as C#) have been brought up over and over again and Shaun has stated several times there will be no change here. I don't really see this as being close minded either, I think it was a decision that provides a solid foundation actually. Just about anything else outside of the VB.NET and the open source repository/daily builds is up for community discussion. I definately agree w/ you that its not about the simple website, but I am always very hesitant to adapt to a new MS technology until it has been out for awhile. I am by no means an MS basher, but they have shown in the past that they will yank something that was to be so promosing. (Vista anyone?)

BTW, Mono does have a VB.NET compiler actually compiling code now. I am sure it is not ready for production use, but there is some promise here. I also see the Novell venture as something that will make VB.NET even more possible on non MS machines in the future.

I respect your opinion, and actually think this thread is turning into something informative for the new comers. Just as you asked us to not be closed minded, I ask you to do the same. I know there are developers working w/ DNN using the Presentation Foundation and XAML and I think anything you have mentioned so far can be accomplished one way or another without having to jump through too many hoops.