Even if you don't want to add VB completion, what would you say to a plugin system that could be used to provide intellisense for an arbitrary language?

I think many of us in the community would be willing to write such code for VB, SQL, and whatever else. Meanwhile, you would be getting many extra paying subscribers that are currently dissuaded (I am one).

please release this. I purchased the license , Vb autocomplete support would be so helpfull.

@MikeS: No one is saying C# is hard, copying and pasting code in my existing VB project into LINQPad (and vise versa) is something I do all the time, but who wants to do a code conversion every time?
I would also venture to say that many of us use VB due to the fact that that is the language chosen by developers who preceded us at our respective companies, and changing that decision is no small task.
I would be completely C# if I had the choice...but I don't.

http://msdn.microsoft.com/en-us/roslyn
I believe this is the beginning of what you'll need to accomplish this task...
Will you still charge extra for AutoComplete if Microsoft offers this API for free?

@Tim Murphy: Hear Hear!

@MikeS. Most of the time when I use LinqPad it is a scratch pad. Why would I want to write C# in LinqPad only to copy and reformat into VB.

From your entire comment I doubt "Note that I am fond of VB, more so that C#" is true!

Can I vote this suggestion down? lol. Guys, C# isn't that hard. You just have to declare everything "backwards", (cast)everything and get your squiglys and semis in order. I vote to change this threads suggestion to have brace matching instead.

Really, if LinqPad is going to be a power users tool, then the authors time would be better spent on other features.

Note that I am fond of VB, more so that C#, but I do not state that on my CV or in any job interview;) Blur your eyes, code is code, if then, do while, for next.

Well, I put my money where my mouth is...hopefully vb.net support will come one day....

Why wait voor VB11, what is the difficulty for doing it with the current version? Can we help?

The samples also need to support VB better.
I'm going to wait 12 months and see how this extremely promising tool develops for those of us who do not have time to swap to C#.

Agreed with the previous poster. I got the credit card out, only to read that the language our product uses-is not supported making a purchase pointless.

Joseph, please, please, please would you take the users feedback on this?

I have the same issue with our product, trying to find time to work on the most wanted features. I empathise :).

However, put it in, that will allow me to buy it!

Thank you!
*Note how I already rate this tool :).

A major let down that this top-rated ticket continues to be ignored....

My money for the AutoComplete upgrade will be on it's way to you as soon as this is available.

I would like to see the AutoComplete feature for VB. Thank you for a great product.

Any news on AutoComplete for VB.Net?

argh - paid for auto completion to find it doesent work for VB

Paid for auto-completion even though I mostly use VB.NET. Hopefully VB.NET auto-completion support will be added soon!

If you add Autocomplete for VB.NET, I will be your new customer!

Maybe, just maybe you could add VB to your autocomplete. I am used to SQL Prompt from Red-Gate for SQL. I would love to have it for LINQKING now. If you add it VB programmers will buy it and love that someone cares about VB from the C# comunity!

Yet another request for VB autocomplete support. I went ahead and purchased even though, like nhWilly, I mainly work in VB :(