SnAdminRuntime: different patch dlls per phase about sensenet HOT 5 CLOSED

It can be a better way to configure the additional assembly source in the phase. For example:
<Phase extensions="RelativePathOfMyAdditionalAssembliesDirectory"> ...

from sensenet.

That is what I wanted to avoid, having to explicitly add this to the manifest. As a package creator, why do I have to do that? Why do not we use an automatism like now, only extended with an optional phase index?

from sensenet.

Because the explicit source is more straightforward approach I think

from sensenet.

Ok, deal. We keep the current behavior (if you put a folder called PackageCustomization into your package, we will load those dlls for all phases), and if you define a folder explicitly in the extensions attribute of a Phase, we will load those dlls only for that phase.

from sensenet.

Closed by #31

from sensenet.