Vincent Parrett

It's not really about personal preference, but using the correct unit namespaces, you are asking less of the compiler when it comes to finding units and resolving types etc. This improves compile times and results in less memory usage by the compiler. Unless you are writing code that must compile on versions earlier than XE2 you should be doing this.

@Uwe Raabe any chance you could put this on github? I think a lot more people would be able to find it then.

Perhaps this will help

I can definitely recommend this tool. I ran it over my 4M line project group and it did a fantastic job. The only things I had to manually fix where where I was referencing a type or function with the unit name, e.g SysUtils.StringReplace(....) had to change to System.SysUtils.StringReplace(....). This will also speed up the compile time as the compiler spends less time doing namespace lookups.

Hi Wagner I'm working towards the design time support, it will take a while but I'll get there eventually. Once I have it working I'll email you again and we can see how it will work with your products.

Hi All For those who are interested, I have made some progress on this project, and have uploaded an installer with the command line tool and IDE plugins for XE2-10.4 - it's still very much an alpha version (not feature complete or stable) but at least shows the direction I'm heading in. I have added some quick notes on how to get started with dpm https://github.com/DelphiPackageManager/DPM/blob/master/GettingStarted.md The installer can be found here https://github.com/DelphiPackageManager/DPM The IDE plugin is still a bit rough around the edges but reasonably stable. Note that installing design time packages is still being worked on. Most of my open source projects have package binaries under the releases tab (the getting started notes show what to do with them). It's still some way from being ready for production use, we are still working on a website/package repository. If you are a library author, please do take a look. Creating packages is not at all difficult.

Yes it's a custom written dotnetnuke module (written in c#) - the part that interacts with stripe is quite small. You need to refrence a stripe javascript file on the page, that is the part that actually handles the card number and submits it to stripe, that gives you back a token that you then use to submit a payment request. Our c# code never see's the credit card details, that is all handled client side (in the browser using the stripe api js). See https://stripe.com/docs/payments/accept-a-payment-charges

No it wasn't that much, I think the fees were around AUD$250 (on the original purchase) and the refund around AUD$3000 - not in the office right now to check.

The key is "There are no fees to refund a charge, but the fees from the original charge aren’t returned."

https://stripe.com/docs/refunds#:~:text=There are no fees to,a refund cannot be canceled.

I can highly recommend stripe - https://www.stripe.com - very reliable and they pay weekly (you can choose the payment frequency). My only gripe is that they do not refund the fees when making a refund (apparently due to visa not refunding them) - had a case a few weeks ago where a customer accidently ordered the wrong number of licenses and the partial refund cost me several hundred dollars in fees! I have tried many different payment processors over the years, in my experience, the one's aligned with banks tend to have the worst tech and support.

Yep, that's the main reason we added the feature for, we find uploading to chocolatey fails occasionally - it's so nice to be able to just try again - we've been dogfooding this feature for a while here and I've had to use it a few times now. Yes, you can certainly edit the exported file. It will be checked for validity when imported - that happens before the change is committed (the import is done in a transaction), so if there are errors in the file nothing bad should happen (this is why this feature took so long to develop!).

We are delighted to announce the Release of Continua CI 1.9.2. We have added the following new features: Export and Import: You can now export one or more configurations to a file and import them back from the file into Continua CI. Requeuing Stages: Requeue a failing stage without restarting the build. Multiple Daily Cleanup Rules: Each type of build by-product can now have a different shelf life. https://www.finalbuilder.com/resources/blogs/introducing-the-release-of-continua-ci-version-192 Continua CI is a low cost, easy to use Continuous Integration Server which includes first class support for Delphi (using FinalBuilder or MSBuild) and version control integration with Git, Mercurial, Subversion and more. https://www.finalbuilder.com/resources/blogs/building-delphi-projects-with-continua-ci

FinalBuilder is a fully featured automated build tool, which supports Delphi 3 to 10.4, along with C++Builder 4 or later. FinalBuilder makes it simple to automate your entire build process, from compiling your Delphi projects to compiling and uploading installers, creating ISO's. There are over 600 built in actions, with support for Git, Mercurial, Perforce, Subversion, TFS and many other version control systems. Unlike xml or batch file based systems, with FinalBuilder you can easily debug your build process, with breakpoints, step over, step into etc. Of course FinalBuilder also integrates with Continua CI - our continuous integration server product, and with other CI servers such as Jenkins. Thousands of Software Developers rely on FinalBuilder to automate the build, test and release process. If you are not using FinalBuilder to automate your builds, you are missing out. Download a fully functional 30 day trial version today.

I just had a quick look and it doesn't inspire a lot of confidence. I'm about to evaluate this library - https://www.devart.com/sbridge/ for SFTP (and SSH, FTPS, FTP) - currently using Secureblackbox (.net version) but looking for something faster and more reliable.