• 0

Best IDE/compiler for VB6 or VB.net


Question

Hey!

I'm going to start programming Visual Basic and i'd like some alternatives other than the products from Microsoft.

Google hasn't been a friend of mine in this matter nor the search on this forum. =S

So i hope you guys will be my friends! =D

What i'm looking for is a "Bloodshed's Dev-C++" type for Visual Basic.

What do you guys suggest?

Edited by OfF3nSiV3
Link to comment
https://www.neowin.net/forum/topic/443652-best-idecompiler-for-vb6-or-vbnet/
Share on other sites

10 answers to this question

Recommended Posts

  • 0

Don't compare vb6 to vb.net. They may share some syntax, but they are two totally different beasts.

For IDEs, You have Visual Studio .NET in its major flavors (The free Express editions are nice.), and you have #Develop (SharpDevelop). Personally, I find that while #develop is nice to keep on a flash drive, it doesn't even come close to Visual Studio. Nothing does, really.

As for compilers, in the background you're really only using Microsoft's compiler...unless you use mono. It's built into both IDEs, but if you want to, you can compile vb.net code on any machine with the .NET Framework. You don't even need the SDK. You'll find VBC.EXE in the Microsoft.NET\Framework\vX.X.XXXX\ directory.

  • 0

I absolutely agree that nothing comes close to VS, that's so true, it's because MS knows their own technology so well, they've modelled the best tool which integrates with the language.

If you're conscious about downloading warez, you can get the Visual Basic.NET 2005 Express edition for free from the MSDN website.

You could always just download your favourite text editor and code in that, and compiler with vbc in the .NET SDK, remember that if you're intending to do any sort of GUI work, you'll need a good IDE to speed up the process, and Visual Studio is obviously the best candidate.

But i mean if you want to code raw, doing a GUI in .net is the easiest ever, in comparison to Java's Swing API.

  • 0
  Winston said:
You could always just download your favourite text editor and code in that, and compiler with vbc in the .NET SDK

Why does everything everywhere (Even microsoft's website) say that vbc is included in the SDK? It's included in a fresh install of the framework itself.

  • 0

I was actually meant for VB6 but I guess the express editions are OK for beginners of VB.NET

edit: I'm also curious if you're learning a .NET language why not try C# instead, imo it's better because the syntax is at least a little bit similar to other languages unlike VB.

Edited by James123
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft quietly burying a massive Windows 7 hardware driver feature as Windows 11 kills it by Sayan Sen Last month Microsoft announced a big update for Windows hardware drivers. The company declared that it was killing Windows Device metadata and the Windows Metadata and Internet Services (WMIS). For those wondering what it is, device metadata, as the name suggests, is the collection of additional, user-facing information that an original equipment manufacturer (OEM) provides about a hardware device. The feature was introduced with Windows 7 and can include stuff like icons, logos, descriptive texts, among other things, that help the Windows UI display details about such devices in places like Task Manager or Device Manager. This was a huge deal back in the day when Windows 7 debuted. The company called the feature "Device Stage" and Microsoft described it as a "new visual interface" that essentially worked like a "multi-function version of Autoplay where it displays all the applications, services, and information related to your device." It is often considered synonymous with the Windows "Devices and Printers" Control Panel applet. Neowin did an in-depth overview of the feature when it first launched which you can find in its dedicated article here. The Windows OS was able to obtain the device experience metadata from the WMIS, but now that the feature is being deprecated, Microsoft has begun removing information about Device Stage from its official support documents. Neowin noticed while browsing that a support article regarding automatic Windows hardware drivers was updated for Windows 11 and 10 sometime last year after the release of Windows 11 24H2. Previously, this article was geared for Windows 7 and was much longer. It also contained information about Device Stage, which, as mentioned above, was a headlining feature on Windows 7. In the said article, the section "If Windows can't find information about your device in Device Stage" has been deleted. You can find the archived version of the support page here. Aside from shortening the amount of information on the page, Microsoft has also added some more details on it. The company has now tried to define what the Microsoft Basic Display Adapter is, how updating drivers through Device Manager works, as well as a thorough and detailed troubleshooting section for common hardware driver errors on Windows, including one for USB-C. You can find all the new details on the updated support page here on Microsoft's website.
    • Sounds creepy to say the least. Don't need nor want AI having access to my history. They're claiming it to be an "offline" model now, but how can we guarantee they don't go behind our backs and change that?
    • Exactly! Without those fundamentals you've mentioned, Democracy is literally just Demonstration of Crazy, nothing to be proud of in such system.
    • Still I see almost no ads in mobile Edge unlike Chrome. So their browser is much better at blocking ads than Chrome and it is a fact. It even blocks ads on YouTube and you can add simple custom block filters. Also, Edge still support manifest v2 on desktop, so I'll look for another browser when I start seeing ads again.
    • Considering they consistently release a new version every year, I think it makes perfect sense. There is a minor pain point at the time of the change, so as long as they only change it once, we get over it and end up in a better place. The issue with MS' naming scheme is that they change their mind so frequently. 3.1, 95, 98, ME, 2000, XP, Vista, 7, 8, 8.1 10, there is no consistency. That was the issue, not the choice of naming the OS after the year. Minor correction: Windows 7 was 6.1. Even Windows 10 was version 6.4 at launch, but they retroactively changed it to 10.0 early on, along with an announcement that they would no longer track the kerel version and OS version separately...then proceeded to call Windows 11 version 10.0.2, so yeah, MS sucks at naming.
  • Recent Achievements

    • First Post
      viraltui earned a badge
      First Post
    • Reacting Well
      viraltui earned a badge
      Reacting Well
    • Week One Done
      LunaFerret earned a badge
      Week One Done
    • Week One Done
      Ricky Chan earned a badge
      Week One Done
    • Week One Done
      maimutza earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      481
    2. 2
      +FloatingFatMan
      263
    3. 3
      snowy owl
      238
    4. 4
      ATLien_0
      230
    5. 5
      Edouard
      176
  • Tell a friend

    Love Neowin? Tell a friend!