Allan,

Glad that fixed the problem. Have a nice weekend.

>Hi Cathi,
>
>That's exactly what the issue was. My "test" P.C. had an old version of some of the Component One DLL's in the GAC - once I removed them, the app worked just fine.
>
>Thanks for your help.
>
>Alan
>
>>Hi Allan,
>>
>>It sounds like a versioning problem. Make sure you don't have multiple versions of Component One on your dev machine.
>>
>>>Hi,
>>>
>>>I have a .NET Winforms (VS.Net 2003) app that I'm getting ready to deploy. The app has a business tier written in C#, and the front-end is VB. The back-end is SQL Server 2000.
>>>
>>>The app uses a number of .NET components from third party vendors:
>>>
>>>1. Infragistics
>>>2. TX Text Control
>>>3. ComponentOne
>>>
>>>There are no ActiveX controls used in this app.
>>>
>>>One of the ComponentOne components I'm using provides an alternative to the standard .NET print preview functionality. On the development P.C., the app runs just fine.
>>>
>>>My setup (built using Installshield Express 5) includes the four required files specified by ComponentOne:
>>>
>>>C1.Common.dll
>>>C1.PrintUtil.dll
>>>C1.C1PrintDocument.dll
>>>C1.Win.C1PrintPreview.dll
>>>
>>>On the P.C. I use for testing purposes, I installed my app and all other components (i.e. Infragistics and TX Text control) appear to work propertly - I've installed all the DLL's for the third party controls in the same folder as the executable.
>>>
>>>However the forms that reference the PrintPreview component will not even load. I get this error when attempting to open one of these forms:
>>>
>>>"The located assembly's manifest definition with name 'C1.Common' does not match the assembly reference".
>>>
>>>Any idea what this means? And how to fix this problem? I've submitted a support request to Component One - but I'm hoping someone here will have an insight into this problem. Any assistance would be appreciated.