Sherlock

Yes. It has been this way for some time now. I just trusted them to stick to that plan. Perhaps that was a lucky guess.

It's on the very first dialogue.

I guess anyone who hasn't jumped ship by now just doesn't care anymore. 😞

Well it did have the TXPManifest Komponent. But I don't believe they really used it themselves.

Best practice has always been to just build the command line and execute that. No hassle with DLL changes, no issues with 32Bit vs. 64Bit and last but by far not least: easy testing by just copying the generated command line into a terminal and checking the output.

Did you try to telnet to that port from another machine?

So...what was the problem then? How did you solve it in the end? I bet there is somebody out there still fighting with this issue.

As far as I can tell AP is writing about https://github.com/pyscripter/python4delphi which (in short) is a Python wrapper. It would be cool to script the Delphi IDE with Python, but I consider that to be a construction site worth leaving be at this time.

With so many computers lying around, why is there no room for one with a correctly setup iptables and transparent squid(guard) with updating black lists? Better yet, IPCop + Squid? Windows is simply not safe to be directly connected to the Internet, no matter how much you fiddle around with its security settings. Seriously!

OMG...I just saw, I copied the wrong declarations to the interface. My bad! Corrected here: type TForm1 = class(TForm) Edit1: TEdit; Label1: TLabel; Label2: TLabel; Button1: TButton; MemoLog: TMemo; procedure BtnClick(Sender: TObject); procedure FormCreate(Sender: TObject); procedure OnServiceConnectionChange(Sender: TObject; PushChanges: TPushService.TChanges); procedure OnReceiveNotificationEvent(Sender: TObject; const ServiceNotification: TPushServiceNotification); But good on you, that you spotted the problem and solved it!

Just let the server provide the client with a download link. Using soap to download data is quite cumbersome in my experience. Cumbersome meaning slow...and you might even need to convert binary data to a readable format like base64 server side and reconvert client side, costing more performance.

Ummm, no. those methods are intended to be part of the class TForm1. So add those declarations to the class declaration: type TForm1 = class(TForm) Edit1: TEdit; Label1: TLabel; Label2: TLabel; Button1: TButton; MemoLog: TMemo; procedure BtnClick(Sender: TObject); procedure FormCreate(Sender: TObject); procedure BtnClick(Sender: TObject); procedure FormCreate(Sender: TObject); Like this...

And I bet they hate you for it

Damned be those blogs... The target of this blog is obviously a more experienced clientele, and Marco failed to mention that. What you did in post #4 was half way right. You need to add the declaration of those methods in the interface of the class TForm1 as well - right after FormCreate should be fine.

OK, that is not enough. You need to expand the declaration of your TForm1 class to include the definition of those methods. I suggest you work through some form of Delphi primer first. Just to get to know the basics.

What do you mean "when I do this"? Do you enter those procedure stumps without interface declaration? Please check the documentation on this http://docwiki.embarcadero.com/RADStudio/Rio/en/Procedures_and_Functions_(Delphi)

Slightly OT: dhsPinger has an ominous ring to it. Pinging the DHS sounds like something you should not do lightheartedly.

Aye, there's the rub. I propose exchanging DotNet with <SomeLanguage>. But folks keep saying "I want <SomeLanguage> feature x, because that is so cool, and I simply can't write my application without it". And then we get some half cooked thing which resembles <SomeLanguage> feature x by intent, but is buggy and breaks other stuff...

Something tells me, it was not the team that took that bite...

Yeah, all the cool kids want to JavaScript, while banks and insurance companies are going out of their way to pay regal salaries to those old COBOL geezers. COBOL delivers, where JS just looks shiny.

I didn't read the book, but I'm guessing that only applies when you add those programmers to the same problem. Luckily Delphi has a ton of problems, that could each feed a programmer for at least a month

And in the end, what is the effort worth? Just to say: "In my product 1+1 is still 2 but it looks better than the others".

That will fail quickly for word wrapped captions.

I don't hate them, I just don't need them. 😉

I have gone through the code and replaced those pesky FreeAndNils with FreeMem or Dispose, whatever fit. It compiles fine now, but next step is to redesign the code to get rid of those ancient pointer thingies altogether. Quite annoying. Thanks everyone for your help and insight!