skills.rest
microsoft
microsoftOFFICIAL
Explore all skills by this author →
Website𝕏@OpenAtMicrosoftGitHub

migrating-bond-interfaces

Migrate .NET projects from Microsoft.Bond.Interfaces to Bond.CSharp SDK.

19|2|Updated May 13, 2026
Search Tags:#migration#.NET#serialization#Bond.CSharp#Microsoft.Bond
One-click install
npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill migrating-bond-interfaces
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migrating-bond-interfaces
Source: https://github.com/microsoft/upgrade-agent-plugins/tree/main/plugins/upgrade-agent/extenders/upgrade-dotnet/upgrade/skills/lazy/libraries/migrating-bond-interfaces
Command: npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill migrating-bond-interfaces

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers migrate from the obsolete Microsoft.Bond.Interfaces package to the unified Bond.CSharp SDK, streamlining the transition and ensuring compatibility with modern .NET serialization.

Core Features & Use Cases

  • Package Migration: Automatically updates package references from Microsoft.Bond.Interfaces to Bond.CSharp.
  • Schema Code Regeneration: Generates fresh schema code from .bond files.
  • Namespace Updates: Transforms old namespaces to the new Bond.CSharp namespace.
  • API Differences Handling: Provides guidance on API changes and differences.
  • Build and Verification: Ensures the migration is successful with a build and verification process.
  • Use Case: A developer can use this Skill to update their project that relies on the Microsoft.Bond.Interfaces package to the Bond.CSharp SDK, simplifying the upgrade process.

Quick Start

Run the skill to migrate your project from Microsoft.Bond.Interfaces to Bond.CSharp SDK.

Frequently Asked Questions about migrating-bond-interfaces

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate from Microsoft.Bond.Interfaces to the Bond.CSharp SDK?▼

To migrate from Microsoft.Bond.Interfaces to Bond.CSharp, you can automate package reference updates, regenerate schema code from .bond files, transform namespaces, and verify the build to ensure .NET serialization compatibility.

Why should I migrate from Microsoft.Bond.Interfaces to Bond.CSharp?▼

Migrating from Microsoft.Bond.Interfaces to Bond.CSharp is necessary because the former package is obsolete; the unified Bond.CSharp SDK streamlines the transition and ensures compatibility with modern .NET serialization tools.

How do I update namespaces and regenerate schema code when upgrading Bond serialization packages?▼

Upgrading Bond serialization packages involves transforming old namespaces to the new Bond.CSharp namespace and regenerating fresh schema code from your existing .bond files to maintain serialization compatibility.

Does the Bond.CSharp migration process handle API differences from Microsoft.Bond.Interfaces?▼

Yes, the Bond.CSharp migration process provides specific API guidance to help developers handle API changes and differences that occurred between the obsolete Microsoft.Bond.Interfaces package and the new SDK.

Can I automate package reference updates for my .NET project migrating to Bond.CSharp?▼

Yes, you can automate package reference updates for .NET projects migrating to Bond.CSharp, which automatically replaces obsolete Microsoft.Bond.Interfaces references and runs a build verification process.

What are the limitations of migrating Bond serialization packages to the unified Bond.CSharp SDK?▼

The migration to the Bond.CSharp SDK focuses on .NET projects requiring serialization compatibility; users must review the provided API guidance carefully to address any breaking changes not automatically resolved by namespace transformation.

Related Skills

Explore More Software Engineering Skills→
PlagueHOPlagueHO
1

dotnet-sdk-style-upgrade

Convert legacy .NET project files to modern SDK-style format.

Community
Intermediate
BarryYinBarryYin

kiro-validate-impl

Validate feature-level integration and cross-task consistency across implemented tasks.

Community
Advanced
TabTabGoTabTabGo

expo-cicd-workflows

Generate, edit, and validate Expo EAS workflow YAML files against schema standards.

Official
Basic
MudraMartinMudraMartin

serialization

Select optimal serialization formats for .NET applications using schema-based approaches.

Community
Intermediate