Hello all,
Sorry if this has been discussed before. I am presently using Keepass 2.21 that I had downloaded earlier from http://keepass.info/download.html or more specifically, from here: http://www.professioneinformatica.eu/Products/PortableApplications/tabid...
Keepass has since upgraded to 2.28 but the packager hasn't updated to this version still. I am using this on Win7 and Win8, therefore I was not aware of the default .NET requirement that XP doesn't fulfill in this case.
I am thinking of having a go at creating a .paf for the 2.28 release of Keepass by myself. I might simply use the previous release as my template and create the new PAF.
Does it make sense to share it here? Or are you not going to entertain .NET/Java based portable apps until you get an "official framework" in place for those two kinds of apps?
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
https://portableapps.com/node/21636
Wm
Like I mentioned in the thread, I am targeting 2.28, while the thread you linked is speaking of 2.0.
In general it is always better to roll with the latest release of an application. With this particular application that is related to security, this is compulsory, as newer releases means security issues from older release were fixed.
EDIT: Is there a planned release date for those apps, at least in the near future? The last portable release for keepass was 2.21 and we're already looking at 2.28.
In case you're busy with porting the others first, I am happy to do this one by myself and place the paf.exe link for others to test.
The last release of KeePass Portable 2.x was never. A third party with no association to PortableApps.com or KeePass was packaging an unofficial version which you're using. We did not at any point release it and then stop supporting it.
We do not currently officially support .NET apps. It's not about Windows XP either. .NET is not guaranteed to be available. .NET 2.0/3.0 is installed on Windows Vista and Windows 7 but not available on Windows 8, 8.1 or 10.0 by default. .NET 4.0 is installed on Windows 8, 8.1 and 10.0 by default but must be manually installed on Windows Vista and 7. A .NET exe can specify that it works with 2.0 through 4.0 as KeePass does, though, so it should in theory work on Vista and up out of the box. To add another wrinkle, there are multiple install types of the later releases as well (core vs full, etc) and some apps need full while some just need core. So we need to make sure we have a platform and launcher that can figure all that out.
Sometimes, the impossible can become possible, if you're awesome!
John, I figured as much that the new ones were from a 3rd party with no affiliation to here (I attached the link as to where I downloaded it from in the OP). If my wording were to suggest otherwise, it was unintended.
But the main takeaway from your reply is that, with apps that have a .NET dependency, things get complicated for our platform due to the scenarios you mentioned in the reply.
I think that the best course of action would be to let you people figure things out internally on how to take this the right way.
I'll update my personal copy of keepass to reflect the latest release, and leave it at that (since I have the necessary dependencies needed anyway, it would seem).