change name "VB6 tools for VS.net"
change name "VB6 tools for VS.net"
Of course, you contributors made a good point saying that “VB6” should be part of the tool´s name to clearly distinguish between the classic Visual Basic and the new Visual Basic (that targets .NET). Anyway, I do decline the suggestion because the tool is compatible with Visual Studio (VS.net is an accepted but unofficial term to name the successor of Visual Studio 6 – and that is just wrong). The toolset lives in the Visual Studio ecosystem (as it is today), that´s why the name remains unchanged.
-
S Ten commented
I agree you ought to include VB6 in the name, rather than just 'Visual Basic Tools'.
Otherwise it is difficult to know this has anything to do with the VB6 programming language.
-
Mladen Mihajlovic commented
I agree with this. It's confusing that it's calle Visual Basic Tools for Visual Studio - I thought it was for Visual Basic .NET - and every time want to come back to this site I have to look up the url becuae vbvs is not anywhere near what I understand of this project which is VB6 integration into Visual Studio.
-
JVimes commented
I almost overlooked this tool because I assumed it was for VB.NET. The name should be "VB6 Tools for Visual Studio".
-
Guillaume JAY commented
I agree with Yves : It's about increasing visibility, which means increasing usage, which means increasing your motivation...
I'm searching once a year for a way to a edit a few living dead v6 projects in a modern IDE : I would never have found (directly) your great tools
-
Yves commented
The tool will not work better, but adding the 6 or 6.0 makes it much more clear for who or what the tool is intended for (so it is NOT VB.Net).
By the way, this was not my proposal :). -
Why? Would it work any better, if I do so?