Problems with stdole.dll

Problems with stdole.dll

• Neoki

  I have the same problem. same error message as above. removing references to stdole does not help. Deployment to my own machines seems fine. But to another new install machine with .NET 2.0 it does not work.

  can anyone help

  my program is useless without this! delivery date = yesterday!
  more info on manual gac installation as last resort would help - but this defeats the idea of 1-click install really,

  hope someone can help further, thanks

  Peter

  
  

• drighetto

  I have the problem that when I deploy a VB2005 application to another PC by copying the contents of the Bin folder (i.e. not by One click) I get the message about the missing file stdole.dll. I am using Microsoft Visual Studio 2005
  Version 8.0.50727.42 (RTM.050727-4200)
  Microsoft .NET Framework
  Version 2.0.50727
  Installed Edition: VB Express
  Microsoft Visual Basic 2005 76541-000-0000011-00124
  

  
  If I look in the Project References, there are 12 entries plus system.serviceprocess which is unused but there is no reference to stdole.dll so I cannot delete it as recommended

  
  On my development PC stdole.dll is in 2 folders , namely

  C:\Program Files\Microsoft.NET\Primary Interop Assemblies
  

  C:\Program Files\Common Files\Microsoft Shared\MSEnv\PublicAssemblies

  
  

  Neither of these folders is present on the Deployment PC

  - If I add them and put stdole.dll in them it still does not work (I suspect because of missing registry entries which I do not know how to make)
  

  
  

  One last possible clue. When I deploy to a friend's PC which has had another.net application installed , my application works !
  

  His PC has the folder C:\Program Files\Microsoft.NET\Primary Interop Assemblies and it contains stdole.dll - Is this folder the GAC

  
  

  Any help or advisce you can offer as i have no ideas after spending several hours on this

  Thanks in advance
  

  
  

  
  

• CarrieE.Wells

  Hi M,
  
  gcutil is a commandline tool for the global assembly cache.
  With it you can add assemblies to the GAC.
  And that is the thing I did.
  
  If you call gcutil with - you will get the correct syntax for using it.
  I did nothing more than call
  a.) send the assembly to the other machine
  b.) run this util there to add the assembly to the GAC
  
  Of course this is only a workaround sinc the means of "OneClickDeployment" are not to do such things
  
  Cheers
  
  Manfred
  

• asvi

  Thanks

  I did have a problem with stdole and sorted it out as described in thios thred

  The database problem is still unsolved

  
  

• pschlang

  My problem is similar, in that my clickonce app will not deploy to several users because stdole.dll (7.0.3300.0) was removed from the GAC when they installed Office 2007. I use Office 2003 functionality and the users who have not installed 2007 are still able to install.

  I could solve this in the short term by having each impacted user use gacutil to install stdole.dll in the GAC - in my case C:\Windows\Assembly This is not a long term fix, and of course it requires user skill, priviledge, etc. Also our policy prevents mailing of the required gacutil.exe or stdole.dll - although I can get around that.

  I have tried setting the Publish Status to "include (auto)" and the Download group to "(required)" however this does not solve the problem. It appears that the clickonce loader process beeds stdole to get started I did try removing stdole from my assembly as well but that didn't help.

  I cannot move everyone to Office 2007, so I need to have my deployment reload stdole to the GAC.

  Appreciate any help on this

  
  

• Bobby Ortiz

  Manfred,
  
  Would you please elaborate on the gcutil and what/how you did what you did I'm not familiar with this utility.
  
  Thanks in advance,
  M
  
  

• Navdeep98296

  Hello,
  
  there is another (perhaps better) way (Visual Studio 2.0.50215):
  
  In "Project-Properties" - "Publish" - "Application Files..." - "stdole.dll" set "publish Status" to "Include".
  
  Then it should work!
  
  
  Cya
  
  Steini
  

• NSBS-JAmes

  I didn't found any thing in refrences pointing to stdole
  
  

• ramesh.kvp

  did you solve your problem i have the same problem. Please can you help me

  
  

• Roland Burt

  This is a known bug in Beta2 & is being addressed.
  
  To workaround this problem, open your project references & delete the refernce to stdole.dll
  

• RozLee

  Hi Manni,
  
  It's right that stdole.dll isn't installed in GAC. But in my case all works perfect.
  
  I tried it with three machines, which have never seen a VS. I used the complete installation ("RUN" installing .NET 2.0 RT and "launch" starting the client).
  
  I didn't know that you need it in GAC. In my case (also using MapPoint Control and another c++ project) it works without using the GAC.
  
  
  Cya
  
  Steini
  

• Richard ?usta

  OK, I spent 2 hours on this and then had a beer.

  The solution is simple. Check the VERSION NUMBER of stdole. You need to chose the right file. I looked at the version numbers on my machine and they all seemed later than the one asked for on the destination machine. So I thought there was no choice - but then I referenced a version of stdole associated with a control - and the correct version number appeared - even though a different version number appeared on the file when you right click and view properties.

  So - if anyone else is stuck - try referencing each of the stdoles on your PC in turn!

  hope this helps - someone might then owe me a beer

  Peter

  
  

• Cloudie

  Thanks for the reply.
  
  I also found a workaround :-)
  I used gcutil to insert stdole.dll in the destinations GAC - then deployment works also!
  
  But I will give your suggestion a try - I'll remove it from the refs and add it as "Content File" to ensure that it is deployed with the application.
  
  Cheers
  
  Manfred
  

• Chandu_K

  Hi Steini,
  
  did you try it
  I don't think so - because I did it - and yes the file is included but not installed in the GAC - and that makes the problems!
  
  If I am wrong - and you tried it - be sure to try it with a machine where no VS 2005 is installed - just the dotnetfx.exe (.NET 2.0 RT) - nothing more!!
  
  Cheers
  
  Manfred
  
• Problems with stdole.dll