Marc

Thank you so much for your quick response, I appreciate it.

The answer to the issue was never replied... I have a bunch of dynamic Frameworks, all of them private, that I install through cocoa pods. Will the solution of this...

Thanks @alexgarbarev option 2 is what I am exactly looking for but I am still having some issues making this to work. I create a definition based on the parent,...

`-(__autoreleasing id)device { return [TyphoonDefinition withClass:[Device class] configuration:^(TyphoonDefinition *definition) { [definition useInitializer:@selector(initWithName:) parameters:^(TyphoonMethod *initializer) { [initializer injectParameterWith:@"REAL NAME"]; }]; }]; } ` Then I register this assembly with the TyphoonComponentFactory...

@alexgarbarev But on these situations that you are exposing I need to know about the implementations that can be swappable at compile time since I need to know that there...

I see different options here but I don't know what other things could break. I can always create a TyphoonDefinition at runtime with the parent and the new class, and...

I am not quite understanding the TyphoonDefinition withFactory option. Does it mean I need to create my TyphoonDefention withFactory at runtime with the new class? Or that should be defined...

@alexgarbarev Do you happen to have an example on TyphoonDefinition WithFactory where it would work?

I just wanted to provide a way to the consumer of all my "Frameworks" to be able to replace TyphoonDefinitions at runtime without having to know what a typhoon definition...

@alexgarbarev I totally understand your point. But we might have different business cases on why I would like to provide or not the source of an Assembly to the consumer...