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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...There is now a C# version of DotNetNuke!There is now a C# version of DotNetNuke!
New Post
3/26/2011 5:40 PM
I guess what I was wondering is why all this work put into porting this over to C# instead of working on further enhancing the platform itself. But I see your point, if the idea is to target more developers (ie: c# community) then that might be a reason.
New Post
3/26/2011 8:26 PM
Lets be really frank about c# and vb - while I'm sure you would never get microsoft to admit anything - c# is really their highest priority langauge these days - and vb is that anoying uncle that will never go away.

MS use c# internally and they have invested and continue to invest hugely in its positioning as a first class internet citizen ... vb ... not so much.

There is an interesting article on http://www.codeproject.com/KB/dotnet/CSharpVersusVB.aspx that sums up in an excellent way the CULTURAL differences between vb and c#. And possibly says a lot about where DNN has come from and where it is headed.

To summarize:

Conventional arguments between Visual Basic and C# focus on the functionality differences. Since these differences are minimal, it is argued that the choice of VB or C# should remain a matter of personal preference.

These arguments fail to take into account the deep cultural differences between the VB and C# camps.

  1. If an organization is content to write average quality software and has average VB developers, there may be no benefit in switching to C#.
  2. If an organization has an exceptional VB team and wants to continue to improve, there is a real danger in continuing in VB. The danger is that the programmers will leave for opportunities in C#. Once even one top developer does this, the polarization of the group towards the old VB culture may accelerate, thus accelerating the attrition.
  3. An organization with an exceptional VB team should switch to C#. The exceptional VB team will have no problem learning the new syntax, so there is no danger. The team will then reap the benefits of the C# syntax, semantics and culture for years to come.
New Post
3/27/2011 11:46 AM
Shauns blog at http://www.dotnetnuke.com/Resources/B... covers the reasons behind the move - essentially it was done for business reasons not technical reasons, though of course we hope that the choice of c# will attract more developers and hence more downloads/modules etc. (vb.net developers are more accepting of c#, whereas c# developers often look down on vb.net).

Regarding the work, we've leveraging the work that Ben did migrating it initially and then keeping a c# version up to date with core releases. Of course we had some effort (though not as much as you'd think), merging in the c# code and converting some additional items that were contributed to 6.0 that were in vb.net, but it's also a good opportunity for us to do some "spring-cleaning" and tidy up the code and the xml commenting. In addition the c# version offers some additional opportunities e.g. there are code analyzers such as stylecop that we can now utilise, and the refactoring tool (resharper) that DNN Corp employees use is more useful for c# than vb.net.


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
New Post
6/15/2011 12:13 AM
I had develop program with c#.
And try to convert VBA on Access to Dotnetnuke on C#.
It so long time.
New Post
6/16/2011 1:26 AM

I've been meaning to make this comment for some time but was waiting to see what was happening with the DNN development. 

I don't have any issues with DNN moving to C#, I am personally making the switch myself, again, not for technical reasons, but because of market forces.

My big beef is with the decision of not making a 5.6.3 version of the core as the final VB version.  As it has been discussed in the forums, there are outstanding issues that should be resolved.  Related to that is the fact that there are so many changes incorporated into the move to C#, it is not only a language conversion but a lot of architectural changes and features have been added.  You really think that people having issues with 5.6.2 are going to jump to the new 6.0 right away???  With all the changes taking place, it would not be wise for anybody to move to the new core until at least 6.1 or 6.2.  This is typical of any major software upgrade, not just DNN, don't take it personally.

So please, give us a solid, final, 5.6.3 version so that we can use it for the next year or so until DNN TNG is truly stable.

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...There is now a C# version of DotNetNuke!There is now a C# version of DotNetNuke!

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.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out