Re: PB.NET creating ancestor classes in separate assemblies

Any chance this will be fixed before the end of August?

Can they, at least, provide is with a workaround?

Because inability to distribute the ancestors in the PB assemblies increases the development costs by factor of 3 or even higher.