I suggest you ...

Reinstate VB5cce (VB5 Control Creation Edition) free download and support

As subject. Until 6 days ago, https://support.microsoft.com/en-us/help/165524 had a useful description and endorsement of VB5cce which used to be available for free. Myself and my clients use VB5cce. The article was since unceremoniously deleted (no mention of why, simply a broken link).

Please Reinstate it and confirm it is free. Thank you.

It is known we can download it from elsewhere, but my users treated this article as an endorsement that it was free to use and supplied by Microsoft. It worked perfectly on Windows 10 64b etc, so I can't see why MS chose to delete all reference to it. It remains an essential tool for creating and maintaining plug-ins on websites etc. Could someone in Microsoft also explain why it was removed? (It is tempting to think that the deletion was a further attempt at alienating and sidelining the VB5 and VB6 community for reasons that can't even be guessed at*).

Googling "VB5cce microsoft" shows right at the top "Visual Basic Control Creation Edition - MSDN - Microsoft" at msdn.microsoft.com/vbasic/downloads/cce/default.asp -- in other words, it is still in googles search cache (but no page cache).

A PDF snapshot is attached. Although I hesitate to share incase you delete this too, it is archived at http://archive.is/GFOyo -- if anyone wants more info, please contact me.

One highlight from the deleted text:

14. *Q. Can I distribute the controls that I create, royalty-free?* A. Yes. Any controls that you create from scratch or any of the intrinsic controls included with the Visual Basic 5 Control Creation Edition may be distributed royalty-free. You may be able to distribute other ActiveX controls, .exe files, and .DLLs that you have purchased, either through Microsoft products or though a third party vendor. Please consult the manufacturer's license agreement for each of files you plan to distribute to determine whether you have the right to distribute the file with your application.

*I make the alienation point above given that VB6 was withdrawn [VB.Net is not a successor] and VB6 users years of skill lost because Microsoft refuses to make it available except as an expensive subscription to MSDN (licence use for development unknown).

Might I respectfully ask VB.Net users to refrain from denigration -- this is a VB5/VB6 question, and we are not trying to compare. :-)

306 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Lofaday - www VB64 com - A new IDE is on its wayLofaday - www VB64 com - A new IDE is on its way shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    7 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Lofaday - www VB64 com - A new IDE is on its wayLofaday - www VB64 com - A new IDE is on its way commented  ·   ·  Flag as inappropriate

        The story of how Microsoft ran itself into the ground..
        The first lesson I learned about "dumb decisions" from Microsoft was when they trashed hardware access when upgrading from Windows 98 and ME. No one noticed that the decision instantly put many thousands of small businesses in trouble, mine included, because the hardware layer access in Windows 98 was the cornerstone of many industrial control systems. All of a sudden I found myself in dozens of meetings explaining to clients why non-NT was no longer made!

        An entire Industrial rack mount computer industry was wiped out overnight. The millions invested in motherboard I/O (including printed circuit boards we developed), now wasted. The information systems I sold each meant many MS OS sales. MS didn't even seem to notice or care that their industrial usage arm was holed below the waterline. (Now, in industrial control solutions, Linux has taken over .. it could have been MS).

        XP is a lot more stable, and indeed most NT based upgrades have been a considerable improvement, but it wouldn't have been rocket science for Microsoft to have added backward compatibility.

        In more general terms, Microsoft need to learn "consistency consistency consistency". The ignorance and arrogance of Microsoft is bewildering if not epic. Ever since Gates left, they seem incapable of applying common sense. Someone in Harvard must have done a popular thesis on obsolescence because MS has adopted it as their mantra! They have abandoned VB6, XNA, SilverLight, Skype API, the original MS Office menus, VS Java, Foxpro, Access, .... Each time they do this, people jump out windows with their careers and businesses in tatters. But Microsoft are just psychopathic at times in their ability to ignore the plight of their own customers. At one point in W8, they even tried to get rid of the desktop! It beggars belief that they expected clients to sit at desks with administrative software running on something that looked more like a giant mobile phone than a desktop PC. Success breeds contempt!

        A great story: Once there were two microprocessor giants, Intel and Motorola. Motorola had the best and fastest 16-bit chips and were set to dominate. Then they both decided to come out with a 32 bit chip. Motorola's was miles better than the Intel 32-bit device. Miles better! BUT Intel did something Motorola decided wasn't important... Intel maintained backward compatibility with their original 16-bit processes. Motorola BETRAYED their own client base. They just stuck up their middle finger and said "go back to school and re-learn". NOW -- how many people have heard of Motorola processors these days? And that's the same dumb mistake Microsoft make over and over again. "CONSISTENCY CONSISTENCY CONSISTENCY".

        The lesson is that when people buy tech, they are making a decision to invest colossal amounts of time in experience in that tech. My customers used to demand Microsoft because they thought the bigger the company, the safer their investment. But now they are just confused. Even banks use opensource.

        Once a company has shown a willingness to betray customer investment with gaay abandon, that company is dead. Teach that one in Harvard!

      • Microsoft, update VB6 programming & VBA programmingMicrosoft, update VB6 programming & VBA programming commented  ·   ·  Flag as inappropriate

        An extended Support Statement from Microsoft for Visual Basic 6.0 on Windows Vista, Windows Server 2008, Windows 7, Windows 8 and Windows 8.1, Windows Server 2012, Windows 10, and Windows Server 2016 ...
        https://docs.microsoft.com/en-us/dotnet/articles/visual-basic/reference/vb6-support

        Microsoft have extended support of VB6 to Windows Server 2016. VB6 is supported until at least November 2027 on Windows Server 2016, and until at least 2025 on Windows 10. Both are likely to be extended.

        VB6 programming is supported on Windows 10, Windows Server 2016 and earlier versions of Windows.

        VBA programming is supported on Office 2016 and earlier versions of Office.

        VBScript programming is still part of Windows.

      • AnonymousAnonymous commented  ·   ·  Flag as inappropriate

        M$, bring this back. It is still needed, and should still be available on your site.

      Feedback and Knowledge Base