Deployment Issues and Library Dependencies

Deployment Issues and Library Dependencies

The TBarCode SDK installs these two libraries:

The .NET Library "TECIT.TBarCode.dll" is also installed into the Global Assembly Cache (GAC), so they are always available system wide. When loading it automatically switches from 32 to 64 bit depending on the process - this has advantages.

The TECIT.TBarCode.dll wants to reload certain DLLs (the TBarCode11.dll / TBarCode11_x64.dll) - the Lib Loader finds these either in the same directory or via the PATH variable, which points to the above path in the Common Files directory. Directly after the SDK installation a server reboot or service restart may be necessary, some services (IIS) read the PATH variable only at startup.

The TBarCode Library needs the Visual Studio Runtime (version dependent), which can be deployed also from here.

SQL Server Deployment

What makes it sometimes tricky are the security features of SQL Server. You can only see what exactly is missing during deployment. In most cases it does not load external DLLs or does not allow file access to reload the other DLLs we need. You have to copy all DLLs (TBarCode*.dll) into a specific SQL Server directory and allow file access in the rssrvpolicy.config file (Full Trust) - see links:

• SSRS -Deploying a Custom Assembly
• SSRS - Asserting Permissions in Custom Assemblies
• SSRS - Using Reporting Services Security Policy Files

If you don’t want to deal with DLL security issues, there is an alternative: You can move the bar code generator into a separate barcode web service and load the bar codes during report runtime 'on-the-fly' from an URL. We deliver the bar code web service with the TBarCode SDK and also a guide how to install and use it: