> 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/learn-more/platform-specifics/deployment.md). # Deployment Learn how to deploy your project with ease! Find all the necessary dependencies and minimum version requirements for PDFNetC in this comprehensive guide. Get ready to distribute your project hassle-fr The following page provides helpful information for deployment. Now that your new project is ready for others to use, it is time to distribute it. ## Dependencies ### **PDFNetC Native library** Our PDFNetC libraries are self-contained and have no external dependencies. ### **.NET Framework (.NET4)** Please see the [.NET 4.5.1+ prerequisites](https://docs.apryse.com/core/learn-more/platform-specifics/pages/GGerl2La8hy2dzX4Azjy#net-framework-451+) for the necessary prerequisites for the .NET framework 4.5.1+. The VC++ v14 runtime libraries need to be either installed on the server (or client desktop), or they may be packaged with your application. ### .NET The .NET "Core" SDK for .NET standard and .NET 5+ is self-contained and has no external dependencies. ### Minimum versions Be sure to check out the **libinfo.txt** file in the `PDFNetC\Lib` folder as it shows what are the minimum version numbers of each language that are required to work with PDFNetC. Note that all the language bindings still need access to **PDFNetC.dll** to work. **Java** The PDFNetC library you download must match the Java JRE architecture (32 or 64 bit). [Link to forum post with more details.](https://groups.google.com/forum/?fromgroups#!searchin/pdfnet-sdk/pdfnetc$20java/pdfnet-sdk/e-izERuN3Ic/UuGZvPWp8JQJ) Furthermore the **PDFNetC.dll** still needs to be available for the **PDFNet.jar** to access. [Link to forum post with more details.](https://groups.google.com/forum/?fromgroups#!searchin/pdfnet-sdk/java/pdfnet-sdk/fr1mR6WLvs8/X0w9ewdny4gJ) **PHP** Before trying PHP be sure to read the additional PHP documentation in the `PDFNetC/Samples` folder. **Python** Read the **libinfo.txt** file for important information when using Python 2. ## Next steps Congratulations, you are now ready to deploy the project to your target/customer computers. Please see the [demo/trial page](/core/learn-more/demo.md) for details regarding the demo/trial mode, and related questions. --- # 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/learn-more/platform-specifics/deployment.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.