The CrystalDecisions package is not visible to any other projects except the first one, why?

[Rod_DOH]

I have to maintain an old VB.NET ASP.NET WebForms app written years ago. I don't know what version of the .NET Framework it was originally written in, because whoever started it didn't put it into any version control and they didn't document it. I've upgraded it to .NET Framework 4.5.2. Recently I migrated all of our TFS repos to GitHub. The original developer added all assemblies/packages using a common pattern from the early 2000s, by adding the DLL to the project, then adding an Imports at the top of every .vb file that needed it. Because the project is now in GitHub, it no longer has the Packages folder that is off the root of the Visual Studio Solution. But that doesn't really matter, because VS re-creates the Packages folder.

Anyway, the problem I'm experiencing is the original developer put the CrystalDecisions.CrystalReports.Engine into multiple projects. I added it to the first project that complained about CrystalDecisions.CrystalReports.Engine not being there, using this syntax:

NuGet\Install-Package CrystalDecisions.CrystalReports.Engine -Version 1.0.0

Which I got off of NuGet 

The problem I'm encountering is I cannot use that same command in Package Manager Console, for any other VS projects. I'll get an error that says CrystalDecisions.CrystalReports.Engine.1.0.0 already exists, so it won't allow me to run it. I had thought that VS would put packages into separate folders for each project, but I'm wrong about that. And VS won't "see" CrystalDecisions.CrystalReports.Engine when I run it. (VS sees it find when I build it, but it won't when I debug it.)

Why does VS not see CrystalDecisions.CrystalReports.Engine in any of the other projects that uses CrystalDecisions.CrystalReports.Engine? How do I get CrystalDecisions.CrystalReports.Engine into all Visual Studio projects that use it?

[Rod_DOH]

I need to add more to what I wrote yesterday. I can build the VS solution locally, but when I try to run it, it always fails, saying, "FileNotFoundException: Could not load file or assembly 'CrystalDecisions.ReportAppServer.CommLayer". But I can find it in the solution, in the local Packages folder. Why does it tell me it cannot find it, but I can find it?

[DonWilliams · Accepted solution]

Hi Rod,

Don't use GitHub, SAP doesn't support it because it's usually out of date and for some reason they change the version.

Go here to get the latest runtime:

https://help.sap.com/docs/SUPPORT_CONTENT/crystalreports/3354091173.html

CR for VS are full builds, meaning it doesn't get patched, and the latest is only version supported, meaning if any issue are found you have to use the latest version, if you replicate the issue SAP will fix it.

Also note the Platforms info:

SAP Crystal Reports for Visual Studio Supported Platforms

Only supported Framework is 4.6, 4.7 and 4.8 because Microsoft no longer supports old versions.

Lots of reasons, security updates are the biggest fixes.

I highly recommend using the latest with 4.8 framework, also, 32 bit runtime is going away so run IIS in 64 bit mode and use CR for VS 64 bit runtime, note due to some legacy dependencies you still need to install both 32 and 64 bit MSI packages.

[Rod_DOH · Accepted solution]

I've been arguing for us to move off of .NET Framework 4.5.2 for at least 5 years. All my arguments have fallen on deaf ears. I don't know why, but there is a HUUUUGEEEE resistance to ever get rid of technical debt.

[DonWilliams · Accepted solution]

One argument is if they want to be Windows Compliant... CR has always fully supported MS end of life time lines... good luck