> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/core/get-started/faq/dotnetcore-dotnet-framework-sdks-feature-performance-parity.md).

# Is there feature/performance parity between .NET Core and .NET Framework SDKs?

Details of parity between .NET Core and .NET Fraemwork (Windows) SDKs for Apryse.

.NET Core has the same performance characteristics as our .NET Frameworks SDKs.

With respect to feature support the two SDKs are identical except for Windows specific features that are not available in .NET Core (which is meant to be cross-platform):

* Interactive PDF viewer (PDFViewCtrl or PDFViewWPF) and associated annotation tools.
* Virtual printer driver
* COM interop Office Conversion
* PDFDCEx for creating a PDF by drawing on Windows Device Context (DC)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.apryse.com/core/get-started/faq/dotnetcore-dotnet-framework-sdks-feature-performance-parity.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.