Desktop Products:

Process Automation:

Software Development:

More Solid Framework testimonials...

Solid Framework Trouble Shooting

Installing Solid Framework

Need Solid PDF Creator?

SolidFramework.dll is what you require to do PDF to Word conversion and PDF modification. If you would like to create PDF files from other file formats, you will need to install Solid PDF Creator. Use the download link from the Downloads tab on the Solid Framework Developer Portal to get the correct version. You don't need a license for the PDF creation printer drivers: they simply inherit your Solid Framework license automatically.

To use the features of Solid Framework, you need a license from Solid Documents. Licenses, including trial licenses, can be created using the self-service Solid Framework Developer Portal. These licenses depend on a machine-specific ID and there is a utility available at the Developer Portal to generate these ids. Importing your license into your application is a one-liner which will look something like this where XXXX is the unlock code. Click here to see video tutorial on how to download the SDK

After completing your download place SolidFramework.dll in the source folder of your project. Add a reference to this assembly from your project, Click here to see video tutorial.

Setting your License

To use the Solid Framework features you must embed the location of your license in your code Click here to see the video tutorial.

// Solid Framework (Professional) license
License.Import(new StreamReader(@"C:\Users\Joe\Documents\Visual Studio 2010\Projects\FrameworkProject\license.xml"));

Finding Office Primary Interop Assemblies

When running your application for the first time, you may get an exception similar to the one shown here. This happens when Solid Framework attempts to use Office from the WordPrintProvider<T> class. This message may appear for the first time when you attempt to deploy to a production machine that does not include Visual Studio.

Could not load file or assembly 'Microsoft.Office.Interop.Word'

Visual Studio uses a private set of primary interop assemblies for Office. This can cause unexpected problems when deploying your solution to an environment that does not have Visual Studio installed.

Microsoft suggests two solutions:

  • Full Office Install: Install the primary interop assemblies at the same time you install Office
  • Redistributable: Run the Microsoft redistributable installer after installing Office

For specific instructions on acquiring and installing the redistributable installer, please read this MSDN topic.


We use cookies on this site to enhance your user experience. By continuing to use this website you are giving consent to set cookies. Please see our privacy policy for more details.
©2000-2021 Solid Documents Limited - Tüm Hakları Saklıdır