Could not find file 'Microsoft.Windows.CommonLanguageRuntime, Version=2.0.50727.0

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • JustRun
    New Member
    • Mar 2008
    • 127

    #1

    Could not find file 'Microsoft.Windows.CommonLanguageRuntime, Version=2.0.50727.0

    I have two windows application projects in the same solution, The solution contains an application that has a reference to another application in the same solution,

    When I tried to publish the project that contains the reference it gave me that error :

    Error 8 :Could not find file 'Microsoft.Wind ows.CommonLangu ageRuntime, Version=2.0.507 27.0

    And another question:
    If I will use the project 1 with all my project is it correct to make it Windows application and add reference to all other projects, or is there better way?
  • balame2004
    New Member
    • Mar 2008
    • 142

    #2
    Change CopyToLocal property of the reference in your project to be true and check it out.

    Comment

    • JustRun
      New Member
      • Mar 2008
      • 127

      #3
      It is True already !!!!!!!!!!!!!!! !!!!!!!!

      Comment

      • IanWright
        New Member
        • Jan 2008
        • 179

        #4
        It sounds like .NET 2.0 isn't installed correctly on the machine or something similar. The CLR is core .NET stuff, so if it can't be found...

        And yes adding references is the correct way to do that.

        Comment

        • JustRun
          New Member
          • Mar 2008
          • 127

          #5
          I don't Think its the framework, cause I have published the other project, and it worked, and yesterday both of them was working fine, I didn't change a bit :(

          Comment

          • tlhintoq
            Recognized Expert Specialist
            • Mar 2008
            • 3532

            #6
            Instead of just hitting "F5"...
            Right-click on one project (not the entire solution) and click 'build'. See if that works.
            Then do the same for the other.
            Hopefully this will narrow down *where* the problem really is.
            I have seen some very odd solutions that had so many projects dependent on other projects that if they weren't built in the right order, so there was a completed executable in the right path - that everything goes awry.

            Comment

            • JustRun
              New Member
              • Mar 2008
              • 127

              #7
              Of course I did so, and I got the same error after build .

              Comment

              Working...