I just verified the zipped plugin package on a "clean" KP 2.47 portable runs with no problems. Something is interfering with the Fusion loader in your case. KeePass installations include an app config file (KeePass.exe.config) which must be in the same folder as KeePass.exe. For 2.47 it should look like this:

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
	<startup useLegacyV2RuntimeActivationPolicy="true">
		<supportedRuntime version="v4.0" />
		<supportedRuntime version="v2.0.50727" />
	</startup>
	<runtime>
		<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
			<dependentAssembly>
				<assemblyIdentity name="KeePass"
					publicKeyToken="fed2ed7716aecf5c"
					culture="neutral" />
				<bindingRedirect oldVersion="2.0.9.0-2.47.0.0"
					newVersion="2.47.0.21109" />
			</dependentAssembly>
		</assemblyBinding>
		<enforceFIPSPolicy enabled="false" />
		<loadFromRemoteSources enabled="true" />
	</runtime>
	<appSettings>
		<add key="EnableWindowsFormsHighDpiAutoResizing" value="true" />
	</appSettings>
</configuration>

The important parts for plugins are <assemblyIdentity> and <bindingRedirect>. publicKeyToken and newVersion attributes must match the assembly attributes of KeePass.exe. Each KP release will include an updated version of KeePass.exe.config to reflect the release version.

For example, I can replicate the OP behavior when I change "fed2ed7716aecf5c" to "ged2ed7716aecf5c" in the above file.

Note also that the application config file can be overridden by the machine.config file for the .NET framework. So if you happened to have edited that file to modify the above binding, that could be an issue.

Bug Report - Not working on 2.47 #27

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions