Add documentation about DynamicProxy internals #624
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
stakx
force-pushed
the
documentation/dynamicproxy-internals
branch
5 times, most recently
from
8f40e6d
to
470b35e
Compare
stakx
force-pushed
the
documentation/dynamicproxy-internals
branch
from
470b35e
to
acd6a5b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is work in progress. I'm planning on adding much more information, especially about the structure and significance of all those similarly-named internal classes in the
Castle.DynamicProxysub-namespaces. I'll also try to add links from the generated proxy type code examples to the parts of DynamicProxy that are responsible for creating those bits of code.Preview it rendered here.
I'll gladly accept any suggestions and corrections (but it's probably still a little too early to review right now).