Warning: "The referenced component 'System' could not be found."

Does anyone know why (or even better, how to fix) VS 2005 randomly generates warnings like:

"The referenced component 'Some .NET assembly' could not be found."

then when you click on the reference in the Solution Explorer, it magically fixes whatever problem it thought it had

How do I stop these warnings from showing up again

Thanks for any help with this.

dougzhoez



Answer this question

Warning: "The referenced component 'System' could not be found."

  • Jonathan Allen

    I meant .NET 1.1, not 1.0.
  • dlcollison

    Did you had .net 2.0 beta before you installed vs2005 I had similar problem with a different component. uninstalling the beta version is not always clean. Go to <WINDOWS>assembly folder and check if you have multiple copies of System assembly with the same version

    I had to delete multiple copies for my application to run correctly. Hope this helps

    Ravi

  • Angelo_f

    if that is the case you should be using the beta removal tool than deleting the files manually.

    http://blogs.msdn.com/astebner/articles/492809.aspx



  • Kris Nye

    I am using VS2005. No, it's not a convertion from VS2003. I've had it happen on multiple projects but they were all in the same solution. I've also had it happen (in this same solution) across multiple machines.

    dougzhoez


  • Dottj

    I did use beta removal tool and it did not remove everything it is supposed to. So the manual work!

  • foobarX

    Was a fix for this ever found I get the same thing in my project and it is very annoying.

  • Fiksman Evgeny

    it shouldnt as it installed .NET in its own "space" and shouldnt conflict with anything else.

    no idea what to suggest I'm afraid



  • Ogulcank

    interesting.

    Is this a VS2003 -> VS2005 project being converted over

    Does this happen on any project, even if it is a new VS2005 project



  • Spigot

    Nope, never had beta. I do have multiple System assemblies (and many others), not from a beta version though but because I also have .NET 1.0 installed. Would this cause the problem
  • Tdotsoulja

    it would be great if you can create a repro solution and report it to MS. so that we can take a look

    - heejae



  • LiveGadgets

    I get the same annoying warning. Here are the steps:

    1. Open New Web Project - Name it what you like

    2. Change Web.config - Compilation tag - debug="true"

    3. Compile the solution

    3. Right click the solution in Solution Explorer, Add New Project - Windows Class Library - Name it what you like

    4. Compile the class library

    5. Reference the Class Library from the Web Project

    a. Right click References

    b. Add Reference - Browse Tab, Look in ClassLibrary1/bin/Release (I've noticed this may not be an issue if referencing the bin/debug assembly)

    6. Compile the Web Project

    7. Annoying warning visible.

    8. Maybe due to debug="true"

    Best wishes,

    Joe


  • Tomasz24311

    For the record I have the exact same issue.

    Oddly most of them are Copy Local = False.

    If I set them Copy Local = True it flips them back to false.


  • leahcimp

    I get exactly the same issue. Does not hinder the build though, just irritating. Beta products never used. They magically fix when I double click the reference, but when I get latest of the code (or reload the solution), they randomly revert back to the "not found" warning. Very annoying.
  • Milzit

    Is there any way it could be caused by the use of custom project and item templates
  • Warning: "The referenced component 'System' could not be found."