Aleksey Garbarev

Thats' quite easy to add. There is few ways to achieve that. (Add new kind of definition, adjust TyphoonInjectionDefinition etc..)

Can anyone help me with this issue? I'm not very familiar with Carthage.

Your code looks correct from first sight. Try something of this: 1) Try to not override operationsAssembly setter. 2) Make sure that `operationsAssembly` property exists (not only setter/getter) 3) try...

> Getting TyphoonAssemblyAccessor instead of MainVCAssembly instance That's ok > threfore it's unrecognized selector sent to instance Because you should pass collaborating assemblies inside activation. See `activateWithCollaboratingAssemblies` for reference

Ah, you are right regarding "threfore it's unrecognized selector sent to instance". Latest pull request broke that branch.

Hm.. Your assemblies looks right from first sight. I believe it worked for objc. Try to debug it via Xcode debugger. Look at `TyphoonStartup.m` source, and put breakpoint at line...

> TyphoonAssemblyActivator was deprecated. Yes. This one was removed, because Typhoon was changed a lot. Main reason of that change - improve performance. If you want to understand technical details....

> Even so, what would be the fix for FactoryAssembly class ? The correct way to get activated assembly (outside plist or appDelegate bootstrapping): ``` FactoryAssembly *activatedAssembly = [FactoryAssembly activated];...

Does it make sense @vitorhugomagalhaes? Can we close this issue?

Main change is performance improvements. It doesn't swizzle all assembly methods at startup as it does before (it uses proxy instead) and that makes huge performance impact on large projects....