What types of experiences are people having who mix C# module development with VB.NET development in DotNetNuke?

 

In the general debate of VB.NET vs. C# I'm neutral. However, since the core of DNN is written in VB.NET I chose to do most of my DNN work in VB.NET as well. This has worked out quite well for me since I find I’m jumping into the core code to often read how the core classes behave. It also lets me cut-and-paste and reuse tons of code from the core and its modules.

 

Recently I've integrated a C# module into my project and I've been disappointed with my personal productivity. I think many of my problems are due to the cross language support in VS.NET 2003. I'm curious how others have found mixing C# and VB.NET.

• I've found problems with cross language intellisense when C# code calls a VB.NET library. After making changes to the VB.NET library, the DLL must be built before C#’s intellisense can see the changes. When using a common language the changes are seen immediately.  
• I’ve found that simple tasks such as right clicking on a class name and selecting Go To Definition doesn’t work nearly as well in cross language scenarios. In a single language it takes you to the source code line, in cross language it takes you to the object browser.

 So far I’ve found mixing languages to not be a great idea. What have other people found?

Hi Micheal

As you may know, I develop in C# and have no experience in VB.NET besides my DNN core debugging moments (fairly infrequent) and my 7 years of VB classic (which not even time is going to heal ;)

Yes, it does cause probs sometimes - I wanted to use some core code and I spend ages converting it (I like to learn as I go - hence no convertor), but this doesn't happen often...

Hmmm - and yes - I've found the same limitations as you to be quite annoying (the Object browser one particularly so! To summarise though, I would say it doesn't phase me enough to switch to VB.NET and my producitvity doesn't suffer too much, but I think the prime reason is that I use C# at work - so this is the deciding factor - from the sounds of it VB.NET would be the better bet if you were language agnostic..

My 2p ;)

rodneyjoyce wrote:

from the sounds of it VB.NET would be the better bet if you were language agnostic..

Being language agnostic I still prefer C#. but that's just me. Depending on what I am doing I may choose to use VB.Net still. For instance, Pulling a core mod to a new assembly to modify it. Sometime I will still port it though. Converting code back and forth can get a little timely, but mostly because I am not the fastest typer in the world.  I am also like Rodney and don't use a converter. My reasons are different though. I feel I can convert it better then the cheap converters out there. I did this once to a VB.Net app of mine and had to fix the generated code. hehe never again.

I also have seen the same quirks with the object browser. & syntax but I manage to get by. Must be those old notepad and DOS Edit days. 

Dave