The reason the _classes.json exist is because the classes had to be loaded in a particular order. If you notice the files are not loaded in the order they would be listed in a *.ps1 search. The formats.json I think it fine this way but I don't believe the module will load correctly with classes this way.

@DarqueWarrior Yes, I know.
This is why I added a feature to be able to list the base classes explicitly, but load everything else using *.ps1. As you can see, the unit tests still work :)

@DarqueWarrior Yes, I know.
This is why I added a feature to be able to list the base classes explicitly, but load everything else using *.ps1. As you can see, the unit tests still work :)

The newer unit tests load the needed classes explicitly.

$here = Split-Path -Parent $MyInvocation.MyCommand.Path
$sut = (Split-Path -Leaf $MyInvocation.MyCommand.Path).Replace(".Tests.", ".")

. "$here/../../Source/Classes/VSTeamVersions.ps1"
. "$here/../../Source/Classes/VSTeamProjectCache.ps1"
. "$here/../../Source/Private/common.ps1"
. "$here/../../Source/Public/$sut"

Those tests are not testing the module loading. The classes that are needed are loaded in the correct order for the tests. If those classes are loaded in the wrong order everything will fail.

It looks like the code can be used for some files just not the classes.

@DarqueWarrior hmmm... ok, I'll have a closer look then and eventually back out the classes.
Thanks for the hints

@DarqueWarrior I've removed the classes changes