Following assembly cannot be resolved

  • Thread starter Thread starter Orantas Gladkauskas
  • Start date Start date
O

Orantas Gladkauskas

Hello everybody,

I'm using Visual Studio 2003. Everything was fine until yesterday.
I cannot add a WebBrowser or any other COM component on windows form
any more.
Every time I open a form in design mode with WebBrowser added on it I
get such resolver error:

Following Assembly Cannot be resolved:
Interop.ShDocVw, Version=1.1.0.0, Culture=Neutral, PublicKeyToken=null

Also this error popups if I create clean C# (VB.NET) project and put
on winform any COM component (WebBrowser, MonthView an etc.)
If i browse to these files then I can work in design mode until i
reopen solution and error happens again. If I dont open form in design
mode that error does not happen and project compiles ok.

Does anybody have any ideas what went wrong?

Orantas
 
same problem since a few days.
the assembly files exist all in the assembly cache.
but it asks everytime for microsoft framework assemblies and for 3rd
party assemblies.

reinstall of .net studio doesnt help!
 
I've built a *Reporting Services Data Processing Extension* and a test applet
that uses it that works fine, but I get this seamingly irrelevant error every
time I load either the solution or a Reporting Services project that uses my
DP extension.

Resolver
Following assembly cannot be resolved:
Don't resolve this assembly
Microsoft.ReportingServices.Interfaces.Version-8.0.242.0,
Culture=neutral, PublicKeyToken-89845cdcd8080cc91
Resolved to:

Note that both the unresolved assembly name and resolved name/path are empty
(null).

It also doesn't seam to matter if I cancel, browse to the local DLL, or
check the don't resolve box and accept. Everything works fine.

I did look for the DLL, and there are about 20 copies on my machine
including every projects \bin\debug and/or \bin\release folder. There are 2
versions on my machine 8.0.242 (11/18/2003) & 8.0.878 (06/15/2004 and a
variety of dates including todays).

I went months without experienceing this problem. I'm not sure what changes
might have triggered it.
 
Back
Top