Vista - Exception Error - Missing dependencies. - Update

<i have also added this reply to the other newsgroup - now that I have
realizd ( and assuming ) it is not a localized error directly to vb.>


I have found this link on the website:
https://www.sdn.sap.com/irj/sdn/busi...ects-downloads

..NET Utility CR 2008 Merge Modules for the .NET Framework ZIP 74.716 Windows
English 12.03.2008
and it states:
===
The Crystal Reports 2008 Runtime Merge Modules may be used to directly embed
the Crystal Reports runtime into your own setup, so it is delivered and
deployed to your users in the same setup package that installs your
application. Un like the Crystal Reports 2008 Runtime redistributable
package, which can be added to another setup in an indirect way (e.g. using
a custom action), the merge modules allow you to tightly embed the Crystal
Reports 2008 Runtime components into your setup. In addition, they are
broken into a core runtime, language packs and mapping support, so they
provide a little bit more flexibility than the standard redistributable
package.
===

I have added the merge modules to my install package.

Now installing the computer does install crystal reports and also creates a
sub folder in my main application called:
CrystalReportsViewers12

BUT:
The same error occurs when running the Crystal Report Viewer from the app:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.FileNotFoundException: Could not load file or assembly
'CrystalDecisions.CrystalReports.Engine, Version=10.5.3700.0,
Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its
dependencies. The system cannot find the file specified.
File name: 'CrystalDecisions.CrystalReports.Engine, Version=10.5.3700.0,
Culture=neutral, PublicKeyToken=692fbea5521e1304'
at WindowsTestApp.Form1.Button3_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons
button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
IntPtr wparam, IntPtr lparam)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value
[HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind
failure logging.
To turn this feature off, remove the registry value
[HKLM\Software\Microsoft\Fusion!EnableLog].



************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase:
file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
WindowsTestApp
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase:
file:///C:/Program%20Files/Company%20Orange%20Inc/SetupTestApp/WindowsTestApp.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.1433 (REDBITS.050727-1400)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Data.DataSetExtensions
Assembly Version: 3.5.0.0
Win32 Version: 3.5.21022.8 built by: RTM
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Data.DataSetExtensions/3.5.0.0__b77a5c561934e089/System.Data.DataSetExtensions.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.





"Miro" <miro@xxxxxx> wrote in message
news:%23J262v08IHA.5928@xxxxxx

"Miro" <miro@xxxxxx> wrote in message
news:ugv1Bx18IHA.4140@xxxxxxfwiw, if you install and setup VPC, you'll never have to worry about having
a "clean" spare PC hanging around... it's *perfect* for testing installers,
since if something's broken, you simply turn it off and all changes
disappear, leaving you with a "virgin" OS for the next time you need to test
an installer (or anything else). I can't count the number of times its saved
my rear.

I build InstallShield packages (no dotNet here) and before VPC, I had to
physically wipe the drive and restore it from DVD, using Drive Image....
took about 20-30 minutes each time and got to be a huge pain after a short
while... still, anything's better than assuming the installer's doing its
job, just to have an end user tell you something's missing.

Plus, can't beat the price (free)

Virtual PC 2007
http://www.microsoft.com/downloads/d...displaylang=en

It's only drawback is... no support for USB. There are similar products that
do support USB, but they're not free.... and, the first image takes the same
amount of time as installing an OS on a new PC... after that, it's all
"flowers and butterflies" <g>

Virutal PC does not run on Vista Home Premium.

The other machine still has xp.

I don't have a "Server" computer yet so Virtual PC is out still for a while
longer.
Im slowly switching to .net so as I will need an actual server for things
like sql server to properly test later on, but thats all in good time.
First the 'dummy' apps have to work and I have to learn those lessons.

I am still cooked on this crystal report error.
I have even tried the CR10 merge modules - entered my authentication key.
Everything compiles - runs great on my machine and the other machine is
still cooked.

Its going to defenitly be a long weekend.

Cheers'

Miro

"Ken Halter" <Ken_Halter@xxxxxx_Sparingly_Hotmail.com> wrote in message
news:egXIe$18IHA.1428@xxxxxx

I was not able to and from all the reading I have done googling around,

there are no 'merge modules' for visual studio 2008.
The whole confusion is that visual studio 2008 comes with crystal reports.
That is true
Crystal Reports has a version 2008, but the actual version taht vs2008 ships
with is 10.5 basic.

The only solution I have found that works so far is to copy an msi from your
own drive:
C:\Program Files\Microsoft
SDKs\Windows\v6.0A\Bootstrapper\Packages\CrystalReports10_5
and install the msi file on the client machine.

After that the viewer works.

I am still looking for a proper msm file that goes with vs2008 to properly
create a nice setup.exe

Hopefully whoever else is about to have this problem reads this post and
saves them a lot of trouble.
Needless to say, there are plenty of unhappy people posting on google and
newsgroups with the lack of help from business objects on crystal reports
shipped with visual studio's versions.

Miro

"Miro" <miro@xxxxxx> wrote in message
news:eXMlu838IHA.4892@xxxxxx

An Email supplied by somoene at Business Objects explains it all:

===
Miro, Crystal reports 10.5 ships with .NET 2008. There are no msm files for
this version, only a MSI files. This was a MS requirement. If you are
looking for this runtime (CR 10.5), please download it from here:

CRRedist2008_ia64.msi
https://smpdl.sap-ag.de/~sapidp/0120...t2008_ia64.zip
CRRedist2008_x64.msi
https://smpdl.sap-ag.de/~sapidp/0120...st2008_x64.zip
CRRedist2008_x86.msi
https://smpdl.sap-ag.de/~sapidp/0120...st2008_x86.zip


If you are using CR 2008, the msm is available from here:
https://smpdl.sap-ag.de/~sapidp/0120...E/cr120_mm.zip


and the MSI is here:
https://smpdl.sap-ag.de/~sapidp/0120...st_install.zip


===


"Miro" <miro@xxxxxx> wrote in message
news:eni7Fs48IHA.4108@xxxxxx