Cdecl possible in visual studo

[ReneMiner]

and everything else that Microsofts Speakers want to tell would not work because of compatibility-reasons is making up reasons only. Try to open a .hlp file on a cdrom from the time there were cd-roms... You know, in windows 10 not possible. Microsoft engineers are on it since ... Windows 10 was released? One day after users complained they can not open their older help-files any more the developers of Oracle (Delphi) reacted and released a tiny little program that according to microsoft is impossible to develop. I mean how many years we have windows 10?
And now some guy from -i guess russia or eastern europe calls himself "The Trick" (found him on this forum- just check his signature) and is deveoping "Bug-Fix after Bug-Fix" and friendly excuses himself for fixing Bugs that Microsoft developers have overseen - revealing the secrets how this company tries prevent people from using microsoft products in a way the could earn one penny of what MS already claims to be their property. Now cDecl was made impossible and only buggy STD and a "native"-always working format to build exe files but mainly dlls. Its not possible no one can do anything about it people, swallow that and accept it... The trick probably not so good in english just did not understand it and did not listen.

Visual Basic 6 - get yourself an enterprise-edition for free from the ancient cd-rom-collections or find one in your language here - take an iso - cheers. and dont forget to grab a copy of the MSDN for Visual Studio 6, the ServicePack 6 - should fit your chosen language - and since that all was long ago and before the invention of the wheel you might be in the need of this because hooks had the hook once a bug is encountered and still hooked a mouse will crash the whole IDE.

I did not read of the Trick for a couple of weeks. Probably he is fixing the bugs in VS 2019. I remember it has issues with licenses expiring and developers could not open their projects anymore and oops sorry there was probably a mistake when the software was locked with VS and all of a sudden landed on a server where some companies should actually never had access to and oh my god they put it in their shopping cart by clicking the little image and paid for it- now what could anyone have done since no one knew that it happened within the billions of transactions every day on the web...

Yeah, sorry too. Am awaiting a little bugfix na - and what i will do is anyway totally impossible so no fear- it can not happen say the wise men from the big company and no one can do things like that...
Before i forget it here is the trick of the trick - open to share with anyone interested because i am pretty certain they are re-using that pattern since... then... visual studio 3 or so 1994 - as the product keys-system that MS for big money purchased and applied since Vista?
- another oopsie -it was stolen by some evil bad man hacker with a dangerous looking keyboard in his hands and the poor company only has less than a hundred product keys left so they must re-use the same keys over and over again since a couple of years now because they need around 80 of these keys company internal. No employee shall have access to the nudes that the boss - excuse - 'remote support features- should not have, bcause hm hm Boss administrator you know. Employee only network control chief assistant

come on smile a bit - just making fun


@kcVinu i saw the other thread yes - great. VB6 was the origin of the common controls we use still today and vb6 is full unicode and was so far ahead the had to backward develop it to ANSI so vB was able to exchange Data with all other visual studio components. it is so crazy that 2 vb6-apps for communication do the following: App1 send data to App2 simple, no COM just WM_SendMessage APP2 receives Message and signal of app1 that says" Hey i am Part of Visual Studio 6" and App 2 now registering VS98--- tick tick tick communication slows down and app2 converts automatic the unicode to ANSI before it sends the message and app1 receives it and decodes it back to unicode.

Now aint that crazy_