Keepass is without a doubt the first program I install on a new PC. Cant live without it. Love the software. Any chance that Keepass will be converted into a Windows Universal App ? Will be absolutely awesome if I can use it on my tablet and desktop pc ! As you know with UWP apps that compiles into native code the program should startup in half the time.
I think touch as a input really makes for exciting apps to be developed I'm not even talking about Cortana integration. I recently converted one of my winform apps to UWP and I must say I think my winform days are over , for good and I'm glad because the new UWP apps are absolutely awesome. The app feels light and way more responsive than the winform app. Scaling of UWP is just in another league all together.
Last edit: Johan 2016-04-04
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You are aware that with project Centennial you can simply convert / load the win32 app and create an appx package that will work in the Windows Store. Therefor the existing keepass win32 app can be used without any changes and can be converted into a Windows Store app (appx) that will run on a desktop pc. Imagine installing keepass like any other mobile app with one click , same for uninstalling.
Also, just to mention that UWP apps in the Windows Anniversary update (June 16) supports extentions , the same extentions that Microsoft Edge browser is using in the new Windows Anniversary version. Therefor no need for an UWP app to create an extention framework because it is build into the UWP framework. And to put cherry on the cake Microsoft is following the Chrome-style extentions. They provide a tool to convert any chrome browser extention to a Microsoft Edge extention.
Last edit: Johan 2016-04-13
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I also wondered that there isn't a UWP-Port for KeePass. On a tablet with touch input it would be a lot easier to use than the existing WinForms-App. Dominik seemed to play around with UWP, you can find the KeePassUAP-Define here and there in the source code of KeePass 2. But when I activate KeePassUAP in KeePassLib I still get a lot of compile errors.
The main problems in KeePassLib from my POV:
1. Namespace "System.Security.Cryptography" does not exist anymore, but algorithms could be ported to using "Windows.Security.Cryptography". I'm not a crypto expert so I don't know how difficult this would be. I assume that the UWP-Crypto is now on par with .NET-Crypto, but the classes look quite different. At some places KeePass-UAP uses the BouncyCastle-Lib but I think it would be better now to use pure UWP-Crypto to get maximum performance.
2. IOConnection has some problems because it uses the non-existent WebClient-Class, should probably be replaced by System.Net.Http.HttpClient.
2. MessageService uses "System.Windows.Forms", a XAML-Port would be necessary.
3. Some small stuff like Cursor.Position, PlatformID, Environment.OSVersion, ...
Yeah, not so much, I think. Dominik separated UI and logic very well. So KeePassLib would have to be ported to UWP and the UI would be needed to be rewritten/redesigned.
Maybe I will give it a shot; it would be easier when KeePass would be managed via GitHub. Any news about this topic?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Of course, there's also a big upside to a single developer - you'll likely never have a change made that unintentionally breaks some other aspect of the program, because the one and only developer is necessarily familiar with all aspects of the program.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Keepass is without a doubt the first program I install on a new PC. Cant live without it. Love the software. Any chance that Keepass will be converted into a Windows Universal App ? Will be absolutely awesome if I can use it on my tablet and desktop pc ! As you know with UWP apps that compiles into native code the program should startup in half the time.
I think touch as a input really makes for exciting apps to be developed I'm not even talking about Cortana integration. I recently converted one of my winform apps to UWP and I must say I think my winform days are over , for good and I'm glad because the new UWP apps are absolutely awesome. The app feels light and way more responsive than the winform app. Scaling of UWP is just in another league all together.
Last edit: Johan 2016-04-04
Search the Mictosoft Store for KeePass. There are some there, such as PassKeep. I know nothing about them except what is in the store.
There is no sign of such a migration and there are plenty of ports, so I don't expect we'll see a UWP anytime soon.
cheers, Paul
Thanks Paul,
You are aware that with project Centennial you can simply convert / load the win32 app and create an appx package that will work in the Windows Store. Therefor the existing keepass win32 app can be used without any changes and can be converted into a Windows Store app (appx) that will run on a desktop pc. Imagine installing keepass like any other mobile app with one click , same for uninstalling.
Also, just to mention that UWP apps in the Windows Anniversary update (June 16) supports extentions , the same extentions that Microsoft Edge browser is using in the new Windows Anniversary version. Therefor no need for an UWP app to create an extention framework because it is build into the UWP framework. And to put cherry on the cake Microsoft is following the Chrome-style extentions. They provide a tool to convert any chrome browser extention to a Microsoft Edge extention.
Last edit: Johan 2016-04-13
I also wondered that there isn't a UWP-Port for KeePass. On a tablet with touch input it would be a lot easier to use than the existing WinForms-App. Dominik seemed to play around with UWP, you can find the KeePassUAP-Define here and there in the source code of KeePass 2. But when I activate KeePassUAP in KeePassLib I still get a lot of compile errors.
The main problems in KeePassLib from my POV:
1. Namespace "System.Security.Cryptography" does not exist anymore, but algorithms could be ported to using "Windows.Security.Cryptography". I'm not a crypto expert so I don't know how difficult this would be. I assume that the UWP-Crypto is now on par with .NET-Crypto, but the classes look quite different. At some places KeePass-UAP uses the BouncyCastle-Lib but I think it would be better now to use pure UWP-Crypto to get maximum performance.
2. IOConnection has some problems because it uses the non-existent WebClient-Class, should probably be replaced by System.Net.Http.HttpClient.
2. MessageService uses "System.Windows.Forms", a XAML-Port would be necessary.
3. Some small stuff like Cursor.Position, PlatformID, Environment.OSVersion, ...
Yeah, not so much, I think. Dominik separated UI and logic very well. So KeePassLib would have to be ported to UWP and the UI would be needed to be rewritten/redesigned.
Maybe I will give it a shot; it would be easier when KeePass would be managed via GitHub. Any news about this topic?
Dominik still manages the changes locally, so a GitHib repository probably won't happen - the downside of having a single developer.
cheers, Paul
Of course, there's also a big upside to a single developer - you'll likely never have a change made that unintentionally breaks some other aspect of the program, because the one and only developer is necessarily familiar with all aspects of the program.