Baatezu wrote
I'm not recommending it, I've never tried it, I just know of it
http://www.rainbowportal.net/ is built off of the same base code (IBUYSPY) as DotNetNuke, but done in C#. Again - Not advocating using it, never have, I like DNN, even though it is in VB. :-P
DotNetNuke and Rainbow source code are not even remotely the same.
"The initial Rainbow design, based on Microsoft's IBuySpy (IBS) portal kit, has been significantly enhanced and improved by a global team of volunteers."
Using Reflector would be okay to view certain sections of DNN's VB.NET code in C#. But you will not get a complete conversion or anything even remotely close to a compilable project in C#.
The core team has gone through great lengths in trying to work with code converter application writers and to this day, there is still not one product out there that will give the 90-95% conversion rate needed to be a viable process.
Even with Reflector, as good of a tool as it is, it still has issues with proper conversion. You will not get an accurate C# representation of DNN's VB.Net source.
To the original poster, why is it important for you to have DNN in a C# version? I only ask because it has come up over the years many times. To this day, there hasn't been one viable reason to provide DNN in a C# version.