Skip to content

Commit 7e77177

Browse files
chore(blog): add blueskyPostId to post frontmatter
1 parent 54574bd commit 7e77177

1 file changed

Lines changed: 1 addition & 0 deletions

File tree

  • src/content/blog/2026/introducing-the-vsix-manifest-designer-visual-studio-extension

src/content/blog/2026/introducing-the-vsix-manifest-designer-visual-studio-extension/index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,7 @@ date: "2026-01-29T12:00:00-05:00"
44
categories: [dotnet, csharp, extensibility, visualstudio]
55
description: "Tired of editing raw XML in your VSIX manifest files? Me too. So I built a modern, visual designer that integrates seamlessly with Visual Studio 2022 and 2026."
66
subtitle: "A modern designer for extension developers!"
7+
blueskyPostId: "3mdkzr5loub2l"
78
---
89

910
I'll be honest - I've been building Visual Studio extensions for years now, and one thing that has always bugged me is editing the `source.extension.vsixmanifest` file. Sure, Visual Studio has a built-in designer, but let's just say it hasn't aged gracefully. It feels clunky, looks outdated, and doesn't play nice with modern SDK-style VSIX projects (like the ones you can create with [VsixSdk](https://www.codingwithcalvin.net/sdk-style-projects-for-your-visual-studio-extensions/)).

0 commit comments

Comments
 (0)