proxying generic interface with inaccessible type parameters throws TypeLoadException about core HOT 6 CLOSED

Hi,

sorry for getting back to you so late. I think it would be worthwhile to give a better message here. Especially that, as you noted, it is currently quite confusing.

from core.

No worries about the delay. I can start working on a fix. Is there a timeline? I'm not going on vacation like last time...

from core.

timeline?

for a release? It's quite fluid :) It's probably better to get a fix sooner rather than later, but the way it's been going we're going to do a release either if there is a major bug fixed (like with v3.2.2) or when we accumulate several smaller fixes (like with v3.2.1

from core.

Okay, thanks. Based on my interpretation of your comments on the urgency of getting this in, I will make this issue my next Open Source work item, but will not allow it to endanger the on time delivery of my grandmother's Christmas present. ;-)

from core.

That sounds reasonable.

BTW, in the long run, the best solution would be to finish the work on generic proxies I spiked in v4 branch (https://github.com/castleproject/Core/tree/4.0-unstable) which would end up, generating FooProxy<T> rather than FooListOfInternalInterfaceProxy but this is a major rewrite of the codebase, so I don't know when it's going to be completed.

Anyway,

Merry Christmas

from core.

Is it yet known when this will be released?

from core.