App Deployment with Crystal Reports and XCOPY (VS2005)

[Liz]

I was intending to use an XCOPY install for a VS2005 C# WinForms app but
when I copied the files and ran the app on a clean machine it failed when it
needed Crystal Reports. Can you not use XCOPY deployment if you have
Crystal Reports dependencies?

Is there an available Crystal redistribution package I can run before doing
my XCOPY deployment?

TIA

 

[Ignacio Machin ( .NET/ C# MVP )]

I was intending to use an XCOPY install for a VS2005 C# WinForms app but
when I copied the files and ran the app on a clean machine it failed when it
needed Crystal Reports.  Can you not use XCOPY deployment if you have
Crystal Reports dependencies?

Is there an available Crystal redistribution package I can run before doing
my XCOPY deployment?

TIA

CR needs merge modules, I do not know of any install setup (a la
dotnetframework.msi), you can create a setup project and install it
like that.

 

[Liz]

message

I was intending to use an XCOPY install for a VS2005 C# WinForms app but
when I copied the files and ran the app on a clean machine it failed when
it
needed Crystal Reports. Can you not use XCOPY deployment if you have
Crystal Reports dependencies?

Is there an available Crystal redistribution package I can run before
doing
my XCOPY deployment?

TIA

<< CR needs merge modules, I do not know of any install setup (a la
dotnetframework.msi), you can create a setup project and install it
like that >>


Thanks, Ignacio ... sounds right; but one thing I noticed is that if you
want to do XCOPY you can create a setup and then use the Crystal MSI that
gets created in the publish directories and run it independently of your
XCOPY.

 

[Ignacio Machin ( .NET/ C# MVP )]

message



<< CR needs merge modules, I do not know of any install setup (a la
dotnetframework.msi), you can create a setup project and install it
like that >>

Thanks, Ignacio ... sounds right;  but one thing I noticed is that if you
want to do XCOPY you can create a setup and then use the Crystal MSI that
gets created in the publish directories and run it independently of your
XCOPY.

Hi,

I have never done it like that, when I have a solution that uses CR I
always create an MSI (at least for the first deployment).