New Maintainer?

[smorks]

as mentioned here: #102 (comment)

i don't actually use this plugin anymore, therefore i don't have the drive or time to maintain this project. i plan on merging in the current two active pull requests (#101, #102), and creating a new release.

beyond that, does anybody want to take over at the maintainer for this project? i can help with any questions about the current codebase, etc.

thanks!

[Silvenga]

I completely depend on KeepassNatMsg, I use it everyday, so I would hate to see it to succumb to entropy overtime. I likely could maintain/help maintain it, I have some OSS experience and I'm a full time .NET developer. Unfortunately, my experience with KeePass plugins is somewhat limited outside of fixing small bugs - so I'm definitely far from an ideal candidate.

[smorks]

#118 might be good yo get to know how messages are passed between the extension and the plugin.

#88 would be mostly plugin work I think.

and #71 for learning how the plugin communicates with the extension maybe.

I'll add you to the repo now.

[Silvenga]

Awesome, thanks!

[Silvenga]

I'll take a crack at #88 - I also have the same issue (I also swear it used to work).

[smorks]

not sure if this will help or if it's something you already know, but for easier debugging, you can compile the plugin in debug, then put in the KeePass's plugins folder, run KeePass, and then use the "Debug -> Attach to Process" option in Visual Studio to make debugging a little easier. Using that should make breakpoints, etc, work.

[Silvenga]

Always a help, thanks.

[EnigmaSolved]

Though I am probably not able to contribute code, I also use KeepassNatMsg daily and am extremely grateful to see @Silvenga being willing to step in as maintainer. 😊

[Silvenga]

Thanks - I appreciate the support. Although, I have to say, RL has been kicking my butt over the past month - hopefully I'll have time to dive-in, in the next couple of weeks.