Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

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
Previous
 
Next
New Post
5/28/2010 4:00 AM
 
Since not everyone in the community are software developers, I would like to explain that the work Ben has already done for a C# version of DNN was the 5000 Ton snowball. Keeping 2 versions in sync at this point does not require that same snowball to keep being lifted over and over again. Just the pieces it picks up while it's still rolling down the hill need to be lifted.

For those worried about double the bugs since there are 2 language versions... The same bugs in theory will wind up in 2 codebases give or take a few code translation mistakes. With eyes looking over both code bases, the chances increase that some of these bugs being discovered quicker.
 
New Post
5/28/2010 6:35 AM
 
hello I recently downloaded dnn c# version and wanted to install 'website' folder in it under localhost.but i got many errors.can u help me please to install and run sln file also??
 
New Post
5/28/2010 12:22 PM
 
I t hink it is a great deal!  I left BASIC back on the Commodore 64 and moved to C.  From there I lived in C/C++ with  a year or so of VBScript until ASP.NET hit. 

For me, it will make my life a LOT easier when I find an issue in DNN or wish to make an enhancement in the core.  Yes, I can manage and dig trhough VB code, but it is not comfortable to say the least.  A few years ago, I dug in the core to add a feature that allowed you to drop of special module into a pane and split the pane into multiple panes.  The way I did it require modifications to the core.  It took me a LOT more time to manage it because of my ineperience with the VB syntax (which I have still never learned to any serious degree).  I never went back and moved those changes to a newer version and scrapped it as I did not have the time.

Back in the day when I had the time, I probably would have contributed a number of things to the core, but the VB syntax was too much time for me. This new version should allow people with time,  to contribute to the core.  I am sure there are quite a number of people such as I, who have never taken the time to "like" the VB syntax.

So, I think it is smart move and will bring in much more benefit to the core.

 
New Post
5/28/2010 12:23 PM
 
Thanks for your work Ben. I tried to use a vb.net to C# translator for DNN and it gave a lot of errors and it was going to take me a lot of work just to make it compile. I told the tool author if he made his tool work for DNN, he can use DNN as his best showcase. DNN (I think?) is the largest open source VB.NET asp.net out there. If it can tackle DNN, it can tackle anything. The author didn't care!
 
New Post
5/29/2010 1:41 PM
 
Dave Buckner wrote:
I want to say thank you to Ben! Your effort in doing this is quite impressive! !

I am not going to say C#, or VB.Net is a better language then the other. The differences to me is mainly in syntax. A little semantics here and there as well maybe, however I think this may matter more if you came from a classic VB background before VB.Net. I myself have used VB since 16 bit VB 3 up to the current version. Once upon a time ago, in a rift of time before .Net 1.1 I bought a great book called C# VB.Net conversion pocket reference. I picked up C# in matter of days! Seeing the differences presented in the manner of that book made a seemingly rough task not so rough. 

Anyway, enough story! This was all leading into (hopefully without being flamed from the VB.Net camp) me saying I prefer C# over VB.Net . C# Is just less wordy to me that's all! Maybe it has a little to do with me being introduced to Pascal before Basic too who knows? :) I do find myself adding semi colons sometimes when working in VB though.

There was some interesting points brought up between here and the blog post. The opening of DNN to a audiance who it was previously closed to seems to have already sparked some interest  

The hot job market for C# devs, and Charles's point # 4 on recruitment should matter the most if it was decided by Corp to switch main development to C#.

On changing core code... I do not suggest at all you change core code!! I will also say that I have seen some core mods in the wild still! I even know of one that has grown along with DNN since the 1x days and is running close to current DNN 5x.

Anyway, just my .2 cents worth ;)



 Dave, I couldn't agree with you more. at the end of the day, both languages go into the same pot and come out the same (CIL) what matters the most to me personally is the syntax and tooling, syntax is more subjective but tooling is defiantly lacking for VB.net.

Take a look at Visual Studio 2010, one of the most valuable new features, Call Hierarchy  isn't available in VB.NET also ReSharper, one of the best addons  for visual studio is missing all of its code analysis features and more in visual basic.

To me the fact that DNN is done in VB.net isn't nearly as annoying as it was when I started working at DNN around  7 months ago (WOW it has been 7 months). It has been mentioned previously,  when it comes to bringing in programmers to join your team or community involvement into development of the product (bugs and patches) I could easily say C# would give you more advantage.

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