Favicon of migrating-cryptography-namespaces

migrating-cryptography-namespaces Skill

AI Agent SkillHTMLOpen source

Migrates System.Security.Cryptography namespace usage from .NET Framework to modern .NET. Analyzes C source files to detect cryptographic type usage and adds the correct using statements and NuGet packages after the namespace split (X509Certificates, Pkcs, Xml). Use when upgrading .NET Framework projects that reference Published by microsoft in upgrade-agent-plugins.

What is migrating-cryptography-namespaces Skill?

Migrates System.Security.Cryptography namespace usage from .NET Framework to modern .NET. Analyzes C source files to detect cryptographic type usage and adds the correct using statements and NuGet packages after the namespace split (X509Certificates, Pkcs, Xml). Use when upgrading .NET Framework projects that reference Published by microsoft in upgrade-agent-plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.

Trust signal
95/100
Maintenance signal
90/100
Adoption signal
23/100

Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.

Key capabilities

  • Includes SKILL.md support
  • Reusable instructions support
  • Security review
  • Research
  • Security review use cases
  • Research use cases

Technical details

Copy skill directory
  • Install or run with Copy skill directory

When to use migrating-cryptography-namespaces Skill

  • Use it for security review.
  • Use it for research.

Built with

HTMLCopy skill directory

Editorial notes

Source

  • Creator: microsoft
  • Repository: microsoft/upgrade-agent-plugins
  • Skill file: plugins/upgrade-agent/extenders/upgrade-dotnet/upgrade/skills/lazy/libraries/migrating-cryptography-namespaces/SKILL.md

What it does

Migrates System.Security.Cryptography namespace usage from .NET Framework to modern .NET. Analyzes C source files to detect cryptographic type usage and adds the correct using statements and NuGet packages after the namespace split (X509Certificates, Pkcs, Xml). Use when upgrading .NET Framework projects that reference

Skill instructions

System.Security.Cryptography Migration Overview In modern .NET, System.Security.Cryptography was split: certificate types moved to System.Security.Cryptography.X509Certificates, CMS/PKCS types to System.Security.Cryptography.Pkcs (separate NuGet package), and XML signature types to System.Security.Cryptography.Xml (separate NuGet package). This skill maps each type to its correct namespace and determines which NuGet packages to add. Workflow Migration Progress: - [ ] Step 1: Detect target framework - [ ] Step 2: Scan source files - [ ] Step 3: Analyze type usage - [ ] Step 4: Add required using statements - [ ] Step 5: Add required NuGet packages - [ ] Step 6: Verify build Step 1: Detect Target Framework Read <TargetFramework or <TargetFrameworks from the project file or Directory.Build.props. If the user specifies a target framework, use that instead. Step 2: Scan Source Files Search for files containing these using statements: - using System.Security.Cryptography; - using System.Secu

Explore related resources

Frequently asked questions

What is migrating-cryptography-namespaces?

migrating-cryptography-namespaces is a open-source AI agent skill with Copy skill directory. Migrates System.Security.Cryptography namespace usage from .NET Framework to modern .NET.

Who is migrating-cryptography-namespaces best for?

migrating-cryptography-namespaces is best for reusing agent instructions, scripts, and references, security review workflows, research workflows.

How do I install migrating-cryptography-namespaces?

Install or run migrating-cryptography-namespaces using Copy skill directory. Check migrating-cryptography-namespaces for the latest setup command.

Is migrating-cryptography-namespaces actively maintained?

migrating-cryptography-namespaces may need a closer maintenance check before production use.

Share:

Stars
8
Forks
1
Last commit
12 days ago
Repository age
2 months
License
NOASSERTION

Auto-fetched from GitHub.

Ad
Favicon

 

  
 

Similar to migrating-cryptography-namespaces