> 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/32bit-64bit-anycpu-dotnet.md). # Is there currently an "AnyCpu" version or only as 32bit or 64bit? World's #1 PDF SDK Library for Web, Mobile, Server, Desktop `Apryse SDK for .NET Framework` is a true .NET component and can be used by any .NET language (e.g. C#, VB.NET, etc). The assembly doesn't use PInvoke or COM interop and does not require/depend on other unmanaged non-system components. At the same, `PDFNet for .NET Framework`, is a "mixed" component and is not "verifiable" since it has some native dependencies (e.g. for printer driver support, XPS printing, GDI, efficient image libs, COM interop etc - these features are by definition impossible to do in "verifiable" .NET components). "AnyCPU" selection means different things in different versions of Visual Studio, however you can definitely make an "AnyCPU" configuration and make the app work correctly on both x86, x64, and other platforms. The issue is not PDFNet specific any there are many solutions: 1. The simplest option is to select 'x86' in your project solution. With this option the app will work on both x86 and x64 system. 2. A bit more complicated option is that you select 'Any CPU' mode in your app. As part of the app install you would copy/install a version of PDFNet that matches the target hardware (i.e. x86, x64). This is possible because both versions have the same signature/cert. 3. Alternatively you can register both the 32-bit as well as 64-bit DLLs in GAC. 4. In case you do not want to haver any app 'installer' and you still want to use 'Any CPU' there are also multiple options some which are outlined here [http://stackoverflow.com/questions/108971/using-side-by-side-assemblies-to-load-the-x64-or-x32-version-of-a-dll](http://stackoverflow.com/questions/108971/using-side-by-side-assemblies-to-load-the-x64-or-x32-version-of-a-dll/). --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.apryse.com/core/get-started/faq/32bit-64bit-anycpu-dotnet.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.