Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...DNN Platform (o...DNN Platform (o...C# Source Code ProjectC# Source Code Project
New Post
5/27/2010 1:17 PM
Regarding Point 7: this "someone" was me ;-)

I know that there will be always new bugs, i was talking about well known bugs, existing since more than 2 or 3 releases. And when talking about "bugs" i do not only mean real bugs but also some "cosmetic issues" many people are complaining about.
When leaving the core and looking at some modules the wishlist with some pretty old items seams not to get shorter. E.g. Blog-Module: having the ability to have more people (or even groups) enabled to edit the SAME blog.

Honestly it could be without any matter for me, as i just started to learn programming modules, but my fear is when two DNNs will exist, the bugs and the list could become more and longer as the same amount of resources will have to deal with two packages.
The only good way should be in my opinion, to switch over at all. But before this the aim should be to get rid of at least the major issues.
Maybe a major version change (5 to 6) could be a good point of time.

New Post
5/27/2010 2:26 PM
Before people get too wrapped up over the level of effort to port and the maintenance costs etc it is important to keep in mind how we arrived at this situation,  A community member, completely independent of DotNetNuke Corp decided that he really wanted/needed a C# version.  He took it upon himself to perform the initial translation and to keep up with bug fixes and enhancements over the last several months.  This required no effort from the core team or the DotNetNuke Core.  When we saw his success we thought it was time we took a fresh look at our position with respect to a C# port.

People can say fix this bug first, add that feature or do this other thing before you spend time on the port, but the reality is the port was already done, and we could either embrace this community contribution or turn our back on it.  In the spirit of Open Source we decided to see how we could use this community member's passion to the benefit of the community.

Some may not see any value in this port, but clearly at least one community member felt it was so important that he spent many hours of his own time to perform the conversion and to keep up with each release (for the record, he finished the 5.4.2 conversion less that 24 hours after the official release of 5.4.2).

Joe Brinkman
DNN Corp.
New Post
5/27/2010 2:38 PM
peter schotman wrote:
Personally, I think this is a complete and utter waste of time. If you can't even state the benefits of one over the other, even the time spend on writing a blog post about it is a waste. One shoud better spend his time on things that really help the community forward (grin).

lol.  Peter, you crack me up *grin*  This is not directed at you, but I will play off of your comment.

One man's passionate endeavor is another mans complete and utter waste of time.

I am never one to get my ire raised too much when people respond to things.  Quite honestly, this is part of what I enjoy about working on DotNetNuke and about open source in general.  People volunteer to work on things that are meaningful to them or rewarding in some way.  Even for two people doing exactly the same thing, their motivations may be completely different.  I find it fascinating and enjoy getting to know the people a little bit and understanding what their passions are.

Nobody should be concerned about the C# version taking precious time away from other efforts.  As we mentioned, this has come about mostly due to the patience and tenacity of a community member.  Ben has been sharing C# versions of the core with us for about 3 months and proven both his desire and ability to keep up with us.  All we're really doing is what we've always done for contributions which is try to establish a way for them to be received and promoted.

I am the FIRST to agree that there are a lot of things to do on the DotNetNuke project.  So pick something and get involved!  If you're unsure how to do that, you can contact me directly and I will help you.  Almost every single one of our community driven module projects could use some help or updates.  There's testing to be done on a regular basis and the Community Teams are constantly in need of folks to help out on projects which serve everyone.

But my main point here is that this does NOT represent a diversion of resources, it represents embracing of contribution by an industrious and reliable community member.  Man I hope we never lose sight of how important that is! *grin* -- It's not always easy or quick to contribute and I just really appreciate that Ben has stepped up to this, been patient and reliable, and committed himself to keeping up with  it.  Whether its a project anyone is particularly interested in or not, it certainly merits a nod of respect.

Scott Willhite, Co-Founder DNN

"It is only with the heart that one can see rightly... what is essential is invisible to the eye. "
~ Antoine de Saint-Exupéry

New Post
5/27/2010 4:33 PM
Personaly I have waited to use DNN with multiple languages for years now. I had not expected that C# should be the second language ;)
But all news in the multi language arena is good news :)

But the most intresting question I have is... Who is Ben ??

New Post
5/27/2010 6:40 PM
Hi Kai,
These well known bugs youre talking about have you got a fix?  If so could you please read http://www.dotnetnuke.com/Community/B... and submit a patch so we can triage that issue into an upcoming release.  Each release we now go through all the issues in Gemini lookinf for submitted code fixes and we usually implement them if they are a good fix.
Thanx for your help.

Philip Beadle - Employee
HomeHomeDevelopment and...Development and...DNN Platform (o...DNN Platform (o...C# Source Code ProjectC# Source Code Project

These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.

Copyright 2017 by DNN Corp Terms of Use Privacy
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out