migrating-to-msmq-messaging

Migrates .NET projects from System.Messaging to MSMQ.Messaging for .NET Core compatibility.

19|2|Updated May 13, 2026
One-click install
npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill migrating-to-msmq-messaging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrating-to-msmq-messaging
Source: https://github.com/microsoft/upgrade-agent-plugins/tree/main/plugins/upgrade-agent/extenders/upgrade-dotnet/upgrade/skills/lazy/libraries/migrating-to-msmq-messaging
Command: npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill migrating-to-msmq-messaging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the migration of .NET projects from using System.Messaging to MSMQ.Messaging, ensuring compatibility with .NET Core and later versions.

Core Features & Use Cases

  • Automated Migration: Converts all necessary references and configurations from System.Messaging to MSMQ.Messaging.
  • Configuration Migration: Transfers queue settings from web.config/app.config to appsettings.json.
  • Dependency Injection: Replaces ConfigurationManager with dependency injection for queue settings.
  • Use Case: Ideal for developers upgrading .NET Framework projects to .NET Core or .NET 5+.

Quick Start

Migrate your .NET project to MSMQ.Messaging using the skill 'migrating-to-msmq-messaging'.

Frequently Asked Questions about migrating-to-msmq-messaging

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

FAQPage Schema
How do I migrate .NET Framework projects from System.Messaging to MSMQ.Messaging?

Migrating from System.Messaging to MSMQ.Messaging is automated by converting project references, configurations, and replacing ConfigurationManager with dependency injection to ensure .NET Core compatibility.

Does this MSMQ.Messaging migration tool move queue settings from web.config to appsettings.json?

Yes, the migration transfers queue settings from web.config or app.config to appsettings.json, replacing legacy ConfigurationManager with dependency injection for .NET Core compatibility.

What is the best way to replace ConfigurationManager with dependency injection for MSMQ queue settings?

The best way to replace ConfigurationManager with dependency injection is through automated migration, which transfers queue settings from app.config to appsettings.json for .NET Core compatibility.

Can I use this System.Messaging migration skill with .NET Framework projects?

No, the migration requires .NET Core or later versions, making it ideal for developers upgrading .NET Framework projects to .NET Core or .NET 5+ with MSMQ.Messaging.

Why does System.Messaging not work with .NET Core and require migration to MSMQ.Messaging?

System.Messaging lacks .NET Core compatibility, requiring migration to MSMQ.Messaging to convert references, update configurations, and implement dependency injection for queue settings.

What are the limitations of migrating System.Messaging references to MSMQ.Messaging?

The migration is limited to .NET Core or later projects, automating reference conversion and configuration transfer from System.Messaging to MSMQ.Messaging without supporting earlier .NET Framework versions.