Works very good & is FAST. Converted around 30 files in 2 secs. Yes has some minor issues with #region, event handler methods BUT does everything else right! Better than me re-writing all the VB code in C#, it cut a lot of time. Fix the couple of issues manually & Voila! Don't understand why anyone needs documentation to click 2 buttons & select a File OR Folder.
!!DOESN'T WORK!! Oh, my word!! Why isn't this on your front/ReadMe page? INSTRUCTIONS: HOW TO START: After installation, open Visual Studio and from the menus, choose VIEW >> Other Windows >> LanguageConverter (A dialog will open) Then, click the [Load file] button or [Folder] button and navigate to the code you wish to convert. OH, great... I got to this point and the actual buttons to do VB >> C# remain gray/disabled. End of wasted time. Off to find a competitor. Bye.
Converted 11/13 files successfully from C# to VB and saved me perhaps about two hours if I had done it manually. Very useful tool, thank you. :)
Be warned that it is an ultra simplistic tool with essentially no customizability and some GUI glitches, but it converted my code correctly with the exception of a 'ListOf' object that I had to tweak a bit. All in all it's still a useful utility.
A couple of more points. I've only tried it on a couple of VB methods, C# needs a break; for each switch/case statement, and VB's With keyword could be easily adapted to C# which has no With keyword, just repeat the object.property for everything within the With. I'm a C#er who has to work on a large VB solution and just find C# much quicker to read and write. And after a conversion it's very easy to spot anything that didn't quite convert right. All in all this extension is a god send, well done!!
-Terrible product, even worse execution. a) Even though this extension is relatively simple it is not intuitive at all. Which is fine, but if something is not intuitive it would be helpfull if you had INSTRUCTIONS. b) Since I do not have instructions on how to get stuff done, I apparently overwrote an entire project by loading in a folder. Thank Heaven I have enough experience to save off a copy of my project and to work on that instead of my mainline project. I also have my code versioned on a server so I would never lose my last check in, but what if I was working on a project. I would be hyper-pissed if I lost two hours of work just because this thing doesn't give you any pop-up boxes or any instructions on how it works or on how best to use it. My recomendation, avoid at all costs and wait for a developer who is doing something more than a college project (and getting an F on it btw) to translate your VB PROJECTS into C#. Just looked into the folder, I didn't over write but instead added. Still documentation would be very helpfull.
Conversion stops on the CoerceIsChatVisible2 function and the region is not converted on version 1.5:
Private Shared Overloads Function CoerceIsChatVisible2(ByVal sender As DependencyObject, ByVal OrigVal As Object) As Object Dim X As P2PChatControl = CType(sender, P2PChatControl) ' Put validation or user interface code in here ' The original value is returned here ' Change code below to do the coersion Dim val as Boolean val = Ctype(OrigVal, Boolean) #End Region
I tried to download this conversion plug-in but got this error:
8/12/2016 11:41:41 AM -
8/12/2016 11:41:41 AM - Searching for applicable products...
8/12/2016 11:41:46 AM - Found installed product - Microsoft Visual Studio Express 2012 for Windows Desktop
8/12/2016 11:41:46 AM - Found installed product - Microsoft Visual Studio Express 2013 for Windows Desktop
8/12/2016 11:41:46 AM - Found installed product - Global Location
8/12/2016 11:41:46 AM - Found installed product - ssms
8/12/2016 11:41:46 AM - VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products.
Do I have to reinstall Visual Studio with a different version? I thought this would work with VS 2013. Am I wrong?
I just hacked the install info so that it'll install into Visual Studio 2013. I haven't tested it yet to see if it causes any sort of incompatibility issues though.