Malformed json due to invalid sample configuration.json

[FokkoVeegens]

I am using version 11.9.47.0 and it seems the configuration.json provided in the folder ConfigSamples (after installation using Chocolatey) is different from this configuration.json: https://github.com/nkdAgility/azure-devops-migration-tools/blob/master/configuration.json. It misses this setting for the source and target configuration: "$type": "TfsTeamProjectConfig". The error I get when running it with this setting is:

[08:30:01 INF] Config Found, creating engine host
[08:30:01 FTL] Your configuration file is malformed and cant be loaded!
[08:30:01 ERR] Could not create an instance of type MigrationTools._EngineV1.Configuration.IMigrationClientConfig. Type is an interface or abstract class and cannot be instantiated. Path 'Source.Collection', line 6, position 17.
[08:30:01 ERR] How to Solve: Malformed Json is usually a result of editing errors. Validate that your C:\repos\CustomerMigration\migrationscripts\Testproject\configuration.json is valid Json!
[08:30:01 INF] Application is shutting down...

After fixing this, I got the following error:

[08:42:41 INF] Config Found, creating engine host
[08:42:41 ERR] The config version 0.0 does not match the current app version 11.9. There may be compatability issues and we recommend that you generate a new default config and then tranfer the settings accross.
[08:42:41 ERR] Unhandled exception!
System.Exception: Version in Config does not match X.X in Application. Please check and revert.

Which was easy to fix by putting 11.9 instead of 0.0 in the "Version" property, but caused by the same issue?

The solution is probably simple, but I guess it's hidden in the pipeline in Azure DevOps.

[MrHinsh]

Have you tried generating a correctly formed json?

We always recommend using the generator and not the examples.

[FokkoVeegens]

Yes, I figured that out 😉, it works with a generated json file. Point is; when a sample is part of the package, it should either work or it should not be in the package.

[MrHinsh]

The configs in the root are used for testing and are not shipped with the product. They are not part of the package.