Skip to content

Conversation

@stakx
Copy link
Member

@stakx stakx commented May 18, 2022

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.DynamicProxy sub-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).

@stakx stakx self-assigned this May 18, 2022
@stakx stakx marked this pull request as draft May 18, 2022 20:23
@stakx stakx force-pushed the documentation/dynamicproxy-internals branch 6 times, most recently from 470b35e to acd6a5b Compare May 19, 2022 12:16
@stakx stakx mentioned this pull request Apr 4, 2023
@304NotModified
Copy link

Maybe we could merge this PR and create new additional PRs in the future if needed? :)

@stakx
Copy link
Member Author

stakx commented Dec 26, 2025

@304NotModified, I was thinking the same earlier. But I should finish with a rough outline of what's still missing, instead of just stopping. 😁

@stakx stakx force-pushed the documentation/dynamicproxy-internals branch from acd6a5b to 8201ae2 Compare December 27, 2025 11:09
@stakx stakx changed the title Add documentation about DynamicProxy internals Start documentation for DynamicProxy internals Dec 27, 2025
@stakx stakx added this to the v6.0.0 milestone Dec 27, 2025
@stakx stakx marked this pull request as ready for review December 27, 2025 11:13
@stakx stakx merged commit dc51147 into castleproject:master Dec 27, 2025
3 of 4 checks passed
@stakx stakx deleted the documentation/dynamicproxy-internals branch December 27, 2025 11:14
@stakx
Copy link
Member Author

stakx commented Dec 27, 2025

@304NotModified, done.

Btw. I always appreciate feedback on the technical documentation that I write. I don't have much practical experience with this kind of work, so I'm probably not in the best position to gauge its quality and comprehensibility. So don't hesitate if you have any suggestions or hints, be it about the documentation's structure, its wording, important missing bits, or anything else.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants