如何在Windows桌面程序中实现类似MAPISendMail的Teams文件发送功能？

Great question—replicating that MAPISendMail workflow for Teams on Windows desktop is totally doable, and you can keep the user experience focused on Teams for recipients/body editing just like you want. Let's dive into the two most reliable approaches:

1. Use Teams URI Protocol (Simplest, Most Direct) #

Teams desktop client supports custom URI schemes that let you launch directly into a new chat window with attachments pre-loaded—this is the closest analog to MAPISendMail you'll get, no API auth required.

How it works: #

• Build a URI that tells Teams to open a blank new chat, with your project file attached. The basic format is:

  msteams://l/chat/0/0?attachment=<URL-ENCODED-FILE-PATH>
  

• URL-encode your local project file path (e.g., C:\MyProjects\CurrentProject.zip becomes C%3A%5CMyProjects%5CCurrentProject.zip). You can use Uri.EscapeDataString() in C# or similar functions in your language of choice.
• Launch this URI from your desktop app using standard process invocation. For example, in C#:

  string filePath = @"C:\MyProjects\CurrentProject.zip";
  string encodedPath = Uri.EscapeDataString(filePath);
  string teamsUri = $"msteams://l/chat/0/0?attachment={encodedPath}";
  Process.Start(new ProcessStartInfo(teamsUri) { UseShellExecute = true });
  

Key Notes: #

• This will open Teams to a blank new chat with your file already attached. Users can then manually add recipients, type the body, and send—exactly what you want.
• Ensure users have the latest Teams desktop client (older versions might not support local file attachments via URI).
• For multiple files, you can add multiple attachment parameters (e.g., &attachment=file2.zip after encoding each path).

2. Graph API + Teams URI (More Reliable for Large/Shared Files) #

If you run into compatibility issues with local file URIs (e.g., large files, restricted file paths), you can combine Graph API with Teams URIs to share files via OneDrive/SharePoint:

Step-by-Step: #

1. Authenticate the user: Use MSAL (Microsoft Authentication Library) for desktop apps to get a Graph API token via interactive login (this pops up a Teams/Office login window if needed).
2. Upload the project file to OneDrive: Call Graph's /me/drive/items/root:/Temp/YourProjectFile.ext/content endpoint to upload the file to a temporary folder in the user's OneDrive.
3. Generate a share link: Use the /me/drive/items/{item-id}/createLink endpoint to get a view/edit link for the file.
4. Launch Teams with the link: Build a Teams URI that pre-fills the message with the share link, letting users add recipients and edit the body:

   msteams://l/chat/0/0?message=Check out this project:%0A<YOUR-SHARE-LINK>
   

Why this works: #

• This avoids any local file access issues, as Teams can reliably pull the file from OneDrive.
• Users still get to handle recipients and body directly in Teams—your app just pre-loads the file link.

Final Recommendation #

Start with the Teams URI protocol first—it's lightweight, no auth required, and matches the MAPISendMail workflow perfectly. If you hit edge cases (like very large files or older Teams clients), fall back to the Graph API approach.

内容的提问来源于stack exchange，提问作者leuk98743