|
-
Mar 3rd, 2005, 05:56 AM
#1
Thread Starter
Hyperactive Member
Crystal Report 10 Deployment
Hi,
My VB.NET application uses CR10 for reporting.
After I build the exe and copy it (as well as CrystalDecision.xxx.xxx.dlls) to another machine which don't have CR10 installed, it throws an exception about COMInterop, and a CLSID. According to that CLSID, I found the dll to be sacommlayer.dll.........is it necessary to build a setup package and can't just XCOPY for deployment? I just use simple report functions.
Thx~
-
Mar 4th, 2005, 02:30 PM
#2
Re: Crystal Report 10 Deployment
Yes, it is necessary to build up a installation package. Controls need to be regisgtered with the operating system, and an installation package will both copy, and register, your controls for you.
-
Mar 7th, 2005, 12:45 AM
#3
Thread Starter
Hyperactive Member
Re: Crystal Report 10 Deployment
But not CR10 already support .NET? Why COM Interop is still necessary?
I just want to completely eliminate this stuff.
-
Mar 7th, 2005, 07:50 AM
#4
Re: Crystal Report 10 Deployment
Yes, CR10 does support .NET, but the end user machine still has to have the necessary dependency files installed on it for everything to work with each other.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|