10 ms·

Your wish is granted. https://github.com/dotnet/roslyn https://github.com/dotnet/roslyn

• lmz 2y ago
  My guess is they want VB6, not VB.NET.
  • giancarlostoro 2y ago
    Correct. There was something really nice about VB6 not needing any special runtime, just bundle any DLLs or OCX files you need and you're golden.
    • chungy 2y ago
      Memories of missing vbrun60.dll come to mind. (or whatever the name of its runtime was)
      • giancarlostoro 2y ago
        It was an installer, installed all the DLLs, which if you bundled with your application, meant you were golden to run it as-is. Though you are technically correct that you need them, I think my statement still stands: You just need to bundle the required DLLs and OCX files and you're golden. https://www.betaarchive.com/wiki/index.php?title=Microsoft_KB_Archive/192461 https://www.betaarchive.com/wiki/index.php?title=Microsoft_K...
        • chungy 2y ago
          That's not very comforting for the dozens of times (that I personally experienced) that the developer didn't make sure it was "golden" and instead left a headache on the end user.
          • rbanffy 2y ago
            As long as you used the bundled installer, everything worked. If you didn’t, you’d need to bundle extra components but, IIRC, component selection was automatic - any DLLs, VBXs, and OCXs used would be detected and bundled. I think the installer itself was licensed from a third party.