There is a new option to automatically convert VB.Net methods with optional parameters to C# overloaded methods. Improved handling of web references so that a web reference with a non-default name converts correctly.

C-Sharpener For VB can automatically convert VB to C# (or as some developers like to spell it VB 2 CSharp ). It is a Visual Studio .NET addin and converts all VB.NET project related files including the project file itself.

You need Visual Studio .NET 2003 or 2005 (Standard, Professional, or Team edition) installed on your computer to run C-Sharpener For VB because it is a Visual Studio .NET Addin. C-Sharpener For VB does not support Visual Studio .Net 2005 Express edition because the Express edition does not support Visual Studio .NET Addins.

C-Sharpener For VB is really a full parser that emits C# instead of MS Intermediate Language. It does full syntactic and semantic analysis including a full symbol tree of all symbols in the code and referenced assemblies. Some conversion problems can only be solved with this level of technology.

If you purchase C-Sharpener For VB, we will give you minor version upgrades for free. For instance, if you license version 1.1 and we release 1.2, you can upgrade for free. If we were to release 2.0, then you would get a substantial discount coupon for the new major release.

C-Sharpener For VB does not convert vbscript. However, it does convert all Visual Basic .NET code in code-behind (*.vb) pages.

Assuming that you have successfully installed C-Sharpener For VB, the menu option should automatically appear. If it doesn't appear, then try the following: Turn on the checkbox to the left of C-Sharpener For VB and click the OK button. The menu option should now appear.

Added automatic edit so that you can just start typing when certain text widgets (Text Box, Button, Group Box, etc.) are selected. Added a Recently Opened Files menu option to the File menu option to make it quicker to open files that you recently opened.

Yes. There is automatic updates which "...is a proactive pull service that automatically downloads and installs Windows updates, such as critical operating system fixes and Windows security patches."

Support for all of the new framework features such as generics, anonymous methods, partial classes, iterators and static classes. See the .NET FAQ for more on these features. Delegate inference is a new feature of the C# compiler which makes delegate usage a little simpler. It allows you to write this: Thread t = new Thread(ThreadFunc); Another minor but welcome addition is the explicit global namespace, which fixes a hole in namespace usage in C# 1.x.

The "transport" layer makes it easy to switch between protocols like HTTP, BEEP and others to fit your application needs. Extensions and the processing of those extensions has been improved and clarified, to ensure more extensibility and interoperability. For more technical details, the SOAP Version 1.2 Part 0 (Primer) has a complete list of changes from SOAP/1.1 to SOAP Version 1.2

Please see Limitations and Workarounds (PDF file) for more details. You may also want to look at some sample converted projects.

For the record, we see value in both the VB.NET and C# languages. However, if C# is your preferred language, you want to convince others to switch from VB. You can use the reasons below to convince your managers or co-workers. Your code quality will improve because C# catches potential errors (example: variable use allowed before initialization and dead code) that are permitted in VB.NET. If your project is a mix of VB.

Several new features have been added, including integration with Apple iTunes, which allows users to create audio files from TropeTrainer software and send them directly to their iPods (or other mp3 players.) Users will also be able to create audio CDs to play in their car. Other features include an improved computer voice, and the ability to play piano sounds behind the voice for enhanced usability.

Solr requires the JUnit JAR for compilation. This JAR is not commited into the Solr lib directory like other dependencies because of the JUnit integration with Ant. Please see the Ant documentation of JUnit for notes about where Ant expects to find the JUnit JAR and Ant task JARs.