Hi,
Check this topic at MSDN:
http://social.msdn.microso
Good Luck
Main Topics
Browse All TopicsI wrote a Visual Basic 2008 application targetting the .NET Framework 2.0. It runs fine on my development PC, but when I run it on a deployment machine, I get the following error:
Could not load file or assembly 'stdole, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=b03f5f7f11d
The deployment PC has .NET Framework 3.5 installed.
The two differences I can see between the two PCs is that the development PC has Visual Basic 6.0, Visual Basic .NET 2003 and Visual Studio 2008, as well as Office 2007, while the deployment PC only has Office 2003. However, my application does not use Office in any way. Here is the stack trace:
************** Exception Text **************
System.IO.FileNotFoundExce
File name: 'stdole, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=b03f5f7f11d
at RadioTracker.frmOptions.Ap
at RadioTracker.frmOptions.cm
at System.Windows.Forms.Contr
at System.Windows.Forms.Butto
at System.Windows.Forms.Butto
at System.Windows.Forms.Contr
at System.Windows.Forms.Contr
at System.Windows.Forms.Butto
at System.Windows.Forms.Butto
at System.Windows.Forms.Contr
at System.Windows.Forms.Contr
at System.Windows.Forms.Nativ
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\F
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\F
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///c:/WINDOWS/Microso
--------------------------
RadioTracker
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files
--------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembl
--------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembl
--------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembl
--------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembl
--------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembl
--------------------------
Interop.DXVUFFT
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files
--------------------------
Interop.MapObjects2
Assembly Version: 2.0.0.0
Win32 Version: 2.0.0.0
CodeBase: file:///C:/Program%20Files
--------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembl
--------------------------
Microsoft.VisualBasic.Powe
Assembly Version: 9.0.0.0
Win32 Version: 3.0.30214.0
CodeBase: file:///C:/Program%20Files
--------------------------
DXVUMeterNET
Assembly Version: 3.0.5.1
Win32 Version: 3.0.6.0
CodeBase: file:///C:/Program%20Files
--------------------------
Microsoft.DirectX.DirectSo
Assembly Version: 1.0.2902.0
Win32 Version: 5.04.00.2904
CodeBase: file:///C:/Program%20Files
--------------------------
AxInterop.MO21legend
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files
--------------------------
AxInterop.MO21ScaleBar
Assembly Version: 2.0.0.0
Win32 Version: 2.0.0.0
CodeBase: file:///C:/Program%20Files
--------------------------
AxInterop.MapObjects2
Assembly Version: 2.0.0.0
Win32 Version: 2.0.0.0
CodeBase: file:///C:/Program%20Files
--------------------------
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembl
--------------------------
MixerProNET
Assembly Version: 1.2.4.0
Win32 Version: 1.2.5
CodeBase: file:///C:/Program%20Files
--------------------------
nxze5nxb
Assembly Version: 0.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembl
--------------------------
Microsoft.DirectX.Direct3D
Assembly Version: 1.0.2902.0
Win32 Version: 9.05.132.0000
CodeBase: file:///C:/Program%20Files
--------------------------
Interop.MO21legend
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files
--------------------------
Interop.MO21ScaleBar
Assembly Version: 2.0.0.0
Win32 Version: 2.0.0.0
CodeBase: file:///C:/Program%20Files
--------------------------
Interop.VBRUN
Assembly Version: 6.0.0.0
Win32 Version: 6.0.0.0
CodeBase: file:///C:/Program%20Files
--------------------------
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembl
--------------------------
System.Transactions
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembl
--------------------------
System.EnterpriseServices
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembl
--------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembl
--------------------------
Microsoft.DirectX
Assembly Version: 1.0.2902.0
Win32 Version: 5.04.00.2904
CodeBase: file:///C:/Program%20Files
--------------------------
gm7sd8yq
Assembly Version: 0.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembl
--------------------------
c9f8kfq6
Assembly Version: 0.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembl
--------------------------
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Hi,
Check this topic at MSDN:
http://social.msdn.microso
Good Luck
I've noticed that the stdole.dll file referenced in my application is apparently in the following folder:
C:\WINDOWS\assembly\GAC\st
However, that folder does not exist on my PC. Maybe that's why it wasn't included in the Setup package? I did, however, find the file in:
C:\Program Files\Microsoft.NET\Primar
which appears to have done the trick. Should I simply manually add this file to the Setup package?
If you insist on using that version of stdOle, add NET 1.1 to the prerequisites of your setup or add stdole.dll to your setup-package.
The difference between the two methods is that the first one will install it in the GAC and that it will be upgraded if needed. The second one will assure that you will always work with that version of the dll, no matter what happens elsewhere.
Business Accounts
Answer for Membership
by: SETPPosted on 2009-09-09 at 00:39:24ID: 25288983
I noticed that even though the file stdole.dll was in my references, it was not included in the Setup package. I manually copied this file to the deployment machine (to the same folder as the EXE) and now it works. Should I simply include this file in my Setup package and everything should be fine?