C# or VB.NET? StyleCop and ReSharper

Coordinator
Nov 1, 2011 at 8:25 PM
Currently we have libraries in C++, C# and VB.NET.

I want to propose the keep the C++ code limited to the ActiveX control and write all the other stuff in C#.
The main benefit is consistency in the code, but also the Express editions of Vis. Studio doesn't allow solutions with mixed projects.
Using just C# we can create 1 solution with all the projects, which will speed up the compile time and simplifies the build process.

Also I want to suggest all C# code for v4.9 must be compliant with the latest StyleCop version (http://stylecop.codeplex.com) and preferable with ReSharper (http://www.jetbrains.com/resharper) as well.
We have a community license from JetBrains we can use with MapWindow.
Jan 4, 2012 at 8:37 PM

I'm in favor of these ideas; as a note, you can create 1 solution that contains VB.NET and C# projects.

Coordinator
Jan 4, 2012 at 8:45 PM

You're right. You can mix languages but that only works with the paid version of Vis. Studio.
If you download the free Express edition you cannot mix languages.

I don't want to start a language war, but I think we should minimize the number of used languages.
The ocx will always be in C++ and I prefer to write all other code in C#.
Most new developers know C# better than VB.NET and the learning curve from java to C# is also much less steeper than from java to VB.NET.

Sticking with VB.NET for new code (and most code for v4.9 will be new) is not very future robust.

--
Paul