I deeply apologize for your frustration. We've actually recently made some changes to our homepage, and added a Documentation Hub with a Frequently asked questions section, in an attempt to make this more clear, but we'll make sure to improve this in the future - it is in everybody's interest.
I have entered this as a new entry on our FAQ page: http://ozcode.userecho.com/topic/1117288-/
As always, we promise to update this ticket as soon as we have an update on the VB.NET support front.
Hi Eli! OzCode is currently not compatible with VB.Net, but you can vote for VB.Net support on this thread.
There are a lot of programmers (especially in US) targeted to vb.net!
Guys, you will become a heroes when start to support it.
It would be fantastic if OzCode can add support for VB.NET. Please add support to VB.NET
precisely my use-case as well! I actually don't need ozcode so much on c# as I'm much more fluent in c# but vb.net is where I sorely miss it as I have to read through other (long gone) peoples' code that's 10s of thousands of lines and peeking & predicticing loop unrolls and expression results as they're happening would make life so much easier. Thank you for considering this feature.
All I use is VB.NET, I'd love to see OZCode available for VB.NET too.
I spent 30 mins watching the videos from the website and reading the docs and quick starting guide etc, because ANYWHERE in the site tells you that this is not Visual Basic.Net compatible, so you guys really need to specify that detail somewhere on the site (on the features page, say its only for C#), because sure many people could buy this software by error figuring that the extension will supports Vb.Net (something that should be obvious to think for a Visual Studio extension...) then that is not an ethic behavior from sellers...
Please think about that... X years so long without specifying that detail in the main site, it sure can give a very bad first impression from potential clients.
The OzCode extension is really awesome, but I will purchase a license for this product only if Vb.Net support arrives.
...but, this public request is 4 years old and that probably means Vb.Net support will never arrive.
Thanks for read!.
Just saw a great demo of OzCode last night in Albuquerque, so sad that VB.NET is not supported. Seems short-sighted to me after people have been requesting it for years! PLEASE make this a priority.
I'm currently working in a place that uses VB.Net, and OzCode compare would really come in handy. Too bad I can't use it. I was all ready to pull the trigger to purchase it just for this project, but sadly you don't support VB.
Its very sad and unbelievable that after a lot of years from the first realease and after 3 years from these kind of threads requesting support for VB.NET lang, a extension for visual studio just support C# and does not support VB.NET.
Two years ago after my last comment in this thread, and this product still be only for C#. Too many people requesting a VB.NET support and the developers ignores them. It is amazing.
I just will never understand why the developers didn't implemented language support for VB.NET, since it is part of .NET platform and since it just need to add some visual elements in the code editor window of VB.NET like it does when putting a breakpoint in C# code editor window. I can't udnerstand.
This is a good solution for debugging LINQ queries and other features... only if you develop in C#. Sad. And they tell us to "vote" in a thread for add support?, really?, maybe in the next five years?. These kind of answers from marketing responsibles/moderators must be a joke, just better say to us that this product will never have support for VB.NET because it was developed by some simple minds whose they does not understand how much they are limitting the expansion of their own product to that 20%-30% market of .NET programmers that develops in VB.NET and not in C#.
Of course this company does not have my money because for VB.NET devs. like me this product is useless... literally it can't be used.
Given the advances made with the Rosyln compiler now there is not supposed to be any difference between the various .Net languages and with so much legacy VB code out there, it's got to be a no-brainer to add support for at least VB.Net if not all .Net languages.
Customer support service by UserEcho