A Programmer with Microsoft tools

Category: pet projects

  • Package Analyzer and show major versions differ

    One of problems in software with packages is when you have 2 projects that reference the same package – but with 2 versions that differ. But it is often very difficult to understand the path that comes to this . PackageAnalyzer identifies this and generate an image  for each package, showing the path : You…

  • MCP Tool vs Swagger–part 3–creation and usage

    Now the idea is to generate from each MCP tool a swagger function. First, we should let the user to choose what MCP to convert to Swagger. This can be done with an Attribute, MCP2OpenAPI.AddMCP2OpenApi Then the problem is what to generate – I decide to generate POST api in an url /api/mcp/{class}/{function} And a…

  • JavaScriptExtensionsAspire–part 2–execution

    Now about the execution of https://www.nuget.org/packages/JavaScriptExtensionsAspire Finding and parsing the package json is pretty easy – this is the code More interessant is to find the name of npm executable Also I want to add the environment variables from the original javascript app Otherwise, pretty obvious stuff of starting the npm process info . NuGet…

  • JavaScriptExtensionsAspire–part 1

    TL;DR: Add package.json commands to ASPIRE Simplifying JavaScript Workflows in .NET with JavaScriptExtensionsAspire As a developer working with .NET and JavaScript, I often find myself juggling between managing JavaScript resources and integrating package.json commands into my applications. It can be tedious and time-consuming. That’s why I’m excited to share my experience with JavaScriptExtensionsAspire, a .NET…

  • Aspire Resource for Aspire–part 4–programatic access

    Aspire 13 has a MCP server integrated https://aspire.dev/dashboard/mcp-server/ . But what about an OPENAPI / swagger ? Also and a graph to show the  resources – https://aspire.dev/dashboard/explore/#resources-page , see graph image. But how about Mermaid syntax display of resources ? So I implemented in https://www.nuget.org/packages/AspireExtensionsResource , version >= 13 . This is how it looks…

  • DocumentorDatabaseExtensionsAspire–part 3–usage

    The usage is pretty simple : add  the package https://www.nuget.org/Packages/DocumentorDatabaseExtensionsAspire to the Aspire host project.  Add an SqlServer database and write //accepts also relative paths var res = db.AddDocumentationOnFolder(@”D:\documentation”); That will be all ! And here it the Aspire Dashboard with documentation for Pubs database And the diagram Here you will find a video about…

  • DocumentorDatabaseExtensionsAspire–part 2–implementation

    The Aspire project as already a database resource  – and a executing one ( sqlpad or dbgate or adminer ) So the answer to the several problems to be solved: 1. How to obtain the tables definition  ? We can obtain the definition by handling ourselves the tables- but why do not profit from the…

  • DocumentorDatabaseExtensionsAspire–part 1–idea

    The Aspire project as already a database resource  – and a executing one ( sqlpad or dbgate or adminer ) What if we can generate documentation for the database  ? There are several problems to be solved: 1. How to obtain the tables definition  ? 2. How to generate documents for the site ? 3.…

  • SqlExtensionsAspire–drop create database

    Another improvement for https://www.nuget.org/account/Packages/SqlExtensionsAspire : Drop Database , Create the database, run init scripts . Demo with Video : https://ignatandrei.github.io/aspireExtensions/images/SqlServerExtensions/video-Recreate_Database_With_Scripts-20251102225854.mp4 The code is pretty simple: executing drop create and initialization

  • Conclusions: Translating fp-filters from TypeScript to C# with AI Assistance

    1. AI Accelerates Porting, but Human Oversight Is Essential AI tools (GPT-4, GPT-5, Claude, Copilot, CodeRabbit) greatly speed up translation and refactoring, but human review is crucial for correctness, especially for edge cases and build issues. 2. Iterative Improvements Work Best Incremental changes—such as improving code coverage, refactoring namespaces, and enhancing documentation—yield better results than…