Just finished my new LINQ to Markdown package– have a try!

[SetTrend]

I am proud to announce I just finished my new LINQ to Markdown Nuget package.

With my new package, .NET now supports the Markdown language natively.

You no longer need to leave the .NET environment and install and run the Node.js runtime or JavaScript packages to read and write Markdown documents.

As far as I know, this is the first time native Markdown support has been available for .NET.

This could be groundbreaking.

---

From the ReadMe.md:

LINQ to Markdown is a Markdown programming interface

LINQ to Markdown is a LINQ-enabled, in-memory Markdown programming interface that enables you to work with Markdown from within the .NET programming languages.

LINQ to Markdown brings the Markdown document into memory. You can query and modify the document, and after you modify it, you can save it to a file or serialize it and send it over the Internet.

• It provides an object model that's light-weight and easy to work with.
• It takes advantage of language features in C# and Visual Basic.

The most important advantage of LINQ to Markdown is its integration with Language-Integrated Query (LINQ). This integration enables you to write queries on the in-memory Markdown document to retrieve collections of Markdown language items, called "tokens". The query capability of LINQ to Markdown is comparable in functionality (although not in syntax) to XPath and XQuery. The integration of LINQ in C# and Visual Basic provides stronger typing, compile-time checking, and improved debugger support.

---

Here's the link to my Nuget package:

https://www.nuget.org/packages/AxDa.Markdown

The story behind this package

I was originally developing a Markdown-to-XAML converter but couldn't find any packages with native Markdown support on NuGet, so I started developing some classes for reading Markdown.

I quickly realized that my Markdown reader was beyond the scope of a local solution, so I outsourced my Markdown code to a separate package.

Intrigued by the LINQ to XML programming interface, I began developing a similar API. However, implementing this API in Markdown proved difficult due to the different semantic types.

Five weeks have now gone into developing this package and writing the documentation. I've written more than 300 unit tests to get the package into a stable state:

Admittedly, the current version of my Markdown package may not fully comply with the CommonMark specification. When I started implementing the package, I based it on the GitHub Markdown implementation, meeting my personal requirements. Hovever, later then I began to adhere to the CommonMark specification. If you notice anything important is missing or not working correctly, I welcome your comments.

I've decided to share my work with the public so that others can benefit from it, too. So here it is.

Next week, I'll also introduce another package family. These are the packages to which this AxDa.Markdown NuGet package originally belonged. They're the reason I created the NuGet packages AxDa.Markdown and AxDa.EnhancedXmlWriter, as well as the tool XDocumentExplorer for testing these packages. I'm currently in the final stages of writing their ReadMe.me files.

---

Looking forward to your comments on this package 🙏 🙌 😊

[Clockwork-Muse]

Discussions in this repo are not an appropriate place to announce a package you have written.

[SetTrend]

OK, I apprehend. Yet, what is the "show and tell" category about then?

[Clockwork-Muse]

I'm sorry, my mistake.
You seem to be all good!

[SetTrend]

Thank you for clarifying! 👍

Would you mind re-opening this discussion then?

[SetTrend]

Thanks!

After I was reading your comment, I added support for a StrikeThroughToken now. It's available in v1.0.2.