dotnet-wcf
Work on WCF services, clients, bindings, contracts, and migration decisions for SOAP and multi-transport service-oriented systems on .NET Framework or compatible stacks.
Install
npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills/tree/main/skills/dotnet-wcf
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install postpartum-genushyacinthus29-dotnet-skills@llmmart
git clone https://github.com/Postpartum-genushyacinthus29/dotnet-skills.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole postpartum-genushyacinthus29/dotnet-skills collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Windows Communication Foundation
Trigger On
- working on WCF services, bindings, or clients
- deciding whether a service should stay WCF or move to modern HTTP APIs
- reviewing transport, security, or interoperability settings
Workflow
- Use WCF where SOAP, WS-* features, or multi-transport service requirements are real; do not rewrite those needs into HTTP-only guidance by accident.
- Keep contracts, bindings, behaviors, and hosting configuration explicit because WCF complexity compounds through configuration indirection.
- For new REST-style services, prefer modern ASP.NET Core APIs instead of extending WCF into a shape it is no longer best suited for.
- Plan migrations per endpoint and capability: transport, security model, transaction requirements, metadata, and client compatibility.
- Validate interoperability and deployment assumptions with the actual client ecosystem, not only local service startup.
- When WCF coexists with ASP.NET, be explicit about which runtime behaviors are shared and which are not.
Deliver
- stable WCF service or client configuration
- realistic migration guidance to newer stacks where appropriate
- clear contract and binding ownership
Validate
- WCF is used for a reason the modern stack does not replace directly
- binding and security behavior are explicit
- interop is verified with real consumers
References
- migration.md - WCF to gRPC/REST/CoreWCF migration paths, decision framework, and endpoint-by-endpoint migration strategy
- patterns.md - WCF maintenance patterns for configuration, contracts, hosting, security, diagnostics, and client proxy management
Files (dotnet-skills)
-
references
-
migration.md 5.5 KB
Loading… -
patterns.md 11.9 KB
Loading…
-
-
SKILL.md 2 KB
--- name: dotnet-wcf version: "1.0.0" category: "Legacy" description: "Work on WCF services, clients, bindings, contracts, and migration decisions for SOAP and multi-transport service-oriented systems on .NET Framework or compatible stacks." compatibility: "Requires WCF or a concrete migration off WCF." --- # Windows Communication Foundation ## Trigger On - working on WCF services, bindings, or clients - deciding whether a service should stay WCF or move to modern HTTP APIs - reviewing transport, security, or interoperability settings ## Workflow 1. Use WCF where SOAP, WS-* features, or multi-transport service requirements are real; do not rewrite those needs into HTTP-only guidance by accident. 2. Keep contracts, bindings, behaviors, and hosting configuration explicit because WCF complexity compounds through configuration indirection. 3. For new REST-style services, prefer modern ASP.NET Core APIs instead of extending WCF into a shape it is no longer best suited for. 4. Plan migrations per endpoint and capability: transport, security model, transaction requirements, metadata, and client compatibility. 5. Validate interoperability and deployment assumptions with the actual client ecosystem, not only local service startup. 6. When WCF coexists with ASP.NET, be explicit about which runtime behaviors are shared and which are not. ## Deliver - stable WCF service or client configuration - realistic migration guidance to newer stacks where appropriate - clear contract and binding ownership ## Validate - WCF is used for a reason the modern stack does not replace directly - binding and security behavior are explicit - interop is verified with real consumers ## References - [migration.md](references/migration.md) - WCF to gRPC/REST/CoreWCF migration paths, decision framework, and endpoint-by-endpoint migration strategy - [patterns.md](references/patterns.md) - WCF maintenance patterns for configuration, contracts, hosting, security, diagnostics, and client proxy management
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.