>Yesterday I found that I didn't have Crystal Reports installed with VS 2008. So I tried rerunning the setup. Of course, setup failed numerous times. So this morning I completely uninstalled and reinstaled VS 2008. VOILA! There's Crystal Reports.
>
>I click Add New Item, then Crystal Report. The report designer opens. I press F6 and get this:
>
>

>Error	1	'CMS.Contact_Single.NewGenerator': no suitable method found to override	
>
>Error	2	'CMS.Contact_Single.FullResourceName': no suitable method found to override
>
>Error	3	Assembly 'CrystalDecisions.ReportSource, Version=10.5.3700.0, Culture=neutral, 
>		PublicKeyToken=692fbea5521e1304' uses 'CrystalDecisions.CrystalReports.Engine, 
>		Version=10.5.3700.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' which has 
>		a higher version than referenced assembly 'CrystalDecisions.CrystalReports.Engine, 
>		Version=10.2.3600.0, Culture=neutral, PublicKeyToken=692fbea5521e1304'	
>		c:\Program Files\Business Objects\Common\2.8\managed\CrystalDecisions.ReportSource.dll	
>
>Error	4	Assembly 'CrystalDecisions.ReportSource, Version=10.5.3700.0, Culture=neutral, 
>		PublicKeyToken=692fbea5521e1304' uses 'CrystalDecisions.Shared, Version=10.5.3700.0, 
>		Culture=neutral, PublicKeyToken=692fbea5521e1304' which has a higher version than 
>		referenced assembly 'CrystalDecisions.Shared, Version=10.2.3600.0, Culture=neutral, 
>		PublicKeyToken=692fbea5521e1304'	
>		c:\Program Files\Business Objects\Common\2.8\managed\CrystalDecisions.ReportSource.dll	
>
>

>
>Mind you now - I didn't do anything to this report. Haven't added data, controls, or anything. My project was compiling fine beforehand.
>
>In the CS file associated with the report are the following usings:
>
>

>using CrystalDecisions.Shared;
>using CrystalDecisions.ReportSource;
>using CrystalDecisions.CrystalReports.Engine;
>

>
>So, here I am again stuck because soime stupid MS product doesn't work. Again I have no reporting capability. I'm beginning to long
>for VFP.

Dealing with references can be a real pain for sure. I often work on projects that have to be synchronized with other installs and end up putting referenced dll's into a folder in the project to make sure everyone references the same ones that work. Since I use so many third party dll's for gps, cameras, scales, or Rfid readers it is really tuff to keep everything at a version level that is supported by everything else. As programmers it is our job to take care of these things so our product we are producing works for out customers.

One thing to consider: If this was easy and had no pain, we wouldn't get paid much for our time. Once you sort out these refrences you might consider documenting them in the event you need to do this again. I don't know how the Crystal Reports stuff works, but I keep pretty close track of the references whenever I update anything, move anything, or change anything.
Tim