Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. Visual Studio
  4. Exceeded retry count of 10. Failed.

Exceeded retry count of 10. Failed.

Scheduled Pinned Locked Moved Visual Studio
helpquestionvisual-studio
4 Posts 2 Posters 5 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R Offline
    R Offline
    Ralf Meier
    wrote on last edited by
    #1

    Since some days I got this message when I try to compile some (not all) of my applications. This happens with vs 2010 and also with vs 2012. This happens on Win7 and also on Win8. I have changed nothing in my application (but I wanted to do that). By googeling the error-message I found, that this is a well known problem since a lot of years (for me since some days - probably 1 week) and I found also severall suggestions (most of them are not working or not helpful) and with some luck one, which works (for me). I have to add some command-lines in the pre-build-events of the application :

    (if exist "$(TargetDir)*old.pdb" del "$(TargetDir)*old.pdb") & (if exist "$(TargetDir)*.pdb" ren "$(TargetDir)*.pdb" *.old.pdb) 2>nul 1>nul
    (if exist "$(TargetDir)*old.dll" del "$(TargetDir)*old.dll") & (if exist "$(TargetDir)*.dll" ren "$(TargetDir)*.dll" *.old.dll) 2>nul 1>nul
    exit 0

    Now I could compile my application again ...:cool: And now the question : Why was it necessary NOW to add those lines to my development-system ... and why (when it is known since a lot of years) is this still a problem - un-independent from the development-system AND the operating-system ? I'm a little bit confused and hope, that someone could explain that to me ...

    L 1 Reply Last reply
    0
    • R Ralf Meier

      Since some days I got this message when I try to compile some (not all) of my applications. This happens with vs 2010 and also with vs 2012. This happens on Win7 and also on Win8. I have changed nothing in my application (but I wanted to do that). By googeling the error-message I found, that this is a well known problem since a lot of years (for me since some days - probably 1 week) and I found also severall suggestions (most of them are not working or not helpful) and with some luck one, which works (for me). I have to add some command-lines in the pre-build-events of the application :

      (if exist "$(TargetDir)*old.pdb" del "$(TargetDir)*old.pdb") & (if exist "$(TargetDir)*.pdb" ren "$(TargetDir)*.pdb" *.old.pdb) 2>nul 1>nul
      (if exist "$(TargetDir)*old.dll" del "$(TargetDir)*old.dll") & (if exist "$(TargetDir)*.dll" ren "$(TargetDir)*.dll" *.old.dll) 2>nul 1>nul
      exit 0

      Now I could compile my application again ...:cool: And now the question : Why was it necessary NOW to add those lines to my development-system ... and why (when it is known since a lot of years) is this still a problem - un-independent from the development-system AND the operating-system ? I'm a little bit confused and hope, that someone could explain that to me ...

      L Offline
      L Offline
      Lost User
      wrote on last edited by
      #2

      Ralf Meier wrote:

      Why was it necessary

      A bug in Visual Studio, perhaps.

      Ralf Meier wrote:

      why (when it is known since a lot of years) is this still a problem

      Only Microsoft could answer that.

      R 1 Reply Last reply
      0
      • L Lost User

        Ralf Meier wrote:

        Why was it necessary

        A bug in Visual Studio, perhaps.

        Ralf Meier wrote:

        why (when it is known since a lot of years) is this still a problem

        Only Microsoft could answer that.

        R Offline
        R Offline
        Ralf Meier
        wrote on last edited by
        #3

        Yes ... of course ... It's a bug in VS or in the Environment around. As I wrote - I have this problem since some days. I don't know what has changed between today and last wednesday either to my system here or at work. In fact nothing changes in my applications which have this problem. Additional - there are severall other applications which don't have this problem. They are still "normal" compilable. But thanks for your response Richard ...

        L 1 Reply Last reply
        0
        • R Ralf Meier

          Yes ... of course ... It's a bug in VS or in the Environment around. As I wrote - I have this problem since some days. I don't know what has changed between today and last wednesday either to my system here or at work. In fact nothing changes in my applications which have this problem. Additional - there are severall other applications which don't have this problem. They are still "normal" compilable. But thanks for your response Richard ...

          L Offline
          L Offline
          Lost User
          wrote on last edited by
          #4

          The point I was trying to make is that this is a Microsoft issue, and you might get better help by asking them.

          1 Reply Last reply
          0
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • World
          • Users
          • Groups