Update VS2003 1.1 window forms for VS2010 with a click once, we also had to update the version of crystal reports used in the application.
Everything works fine if the user has a local administrator. Unfortunately, most of our users are extremely locked and cannot install anything. This creates a problem for installing CR13 binaries. In the click settings, once I checked all the CrystalDecisions files. * Dlls as Include / Required, but they are not published in the deployment folder and, therefore, are not copied to users' computers with other third-party libraries. This means that the application starts normally, but as soon as the user tries to run the report, he receives the following error:
************** Exception Text ************** System.IO.FileNotFoundException: Could not load file or assembly 'CrystalDecisions.Windows.Forms, Version=13.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The system cannot find the file specified. File name: 'CrystalDecisions.Windows.Forms, Version=13.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304'
Even if it is marked as Include / Required, this file does not expand. I really do not want to chase every user and install him manually (we do not have the ability to do group push). There are four Crystal dlls that we use:
- CrystalDecisions.CrystalReports.Engine
- CrystalDecisions.ReportSource
- CrystalDecisions.Shared
- CrystalDecisions.Windows.Forms
Of these, only the engine is actually deployed! Does anyone know why one doesnβt deploy others (for example, Windows Forms dll) and how can I convince it?
thanks!
edit: tried to remove existing links to Crystal dlls (pointing to the Crystal installation under "C: \ Program Files \ SAP BusinessObjects \ Crystal Reports for.NET Framework 4.0 \ Common \ SAP BusinessObjects Enterprise XI 4.0 \ win32_x86 \ dotnet" by copying them to project and adding them through the tab "view", but they still have not been deployed :( Almost the same as their flag is set, to say that they should not be deployed, so the visual studio just ignores them ??
source share