PdfParser.Pro 2.0.1

PdfParser Pro

Command-line PDF parser sold through the separate pdfparser-licensing-site project.

Project Split

Keep these as two separate projects:

C:\Users\maazy\pdfparser-licensing-site
  -> checkout
  -> license emails
  -> license validation API

C:\Users\maazy\RiderProjects\PdfParser
  -> C# parser product
  -> NuGet package / CLI build

That separation is correct. The website should not contain the parser code, and the parser should not contain Stripe/email checkout logic.

Customer Install

The current project is an executable, so the easiest NuGet distribution is a global tool:

dotnet tool install --global PdfParser.Pro --version 2.0.1

Then customers run:

pdfparser activate PDFP_your_license_key
pdfparser path/to/document.pdf

By default the tool validates licenses against:

https://pdfparser-api-fn-43346.azurewebsites.net/api/licenses/validate

For local development or a future custom domain, override the API URL with:

PDFPARSER_LICENSE_API_URL=http://localhost:4242

For local testing before publishing:

dotnet pack PdfParser/PdfParser.csproj -c Release
dotnet tool install --global PdfParser.Pro --add-source PdfParser/bin/Release --version 2.0.1

Developer Library Option

If the target customer is a developer who wants to call the parser inside their own C# app, create a separate class-library package later:

dotnet add package PdfParser.Pro --version 2.0.0

That requires moving the parser class into a library-style API and keeping the CLI as a thin wrapper.