none
Error while trying to run project: Not implemented RRS feed

  • Question

  • Hi All,

    Just out of the blue my VS 2010 solution will no longer debug at all and get the "Not implemented" error message. I tried repairing and re-installing VS 2010 with no luck, rebooting, cleaning solution output files, etc. What I have found if I took this complete solution file and moved to another computer and it runs just fine under debug mode in VS 2010. What and the heck could have happen to my machine or enviornment to cause this issue.

    Any and all feedback is appreciated!

    Thanks,

    Jake

     

    Thursday, July 29, 2010 4:40 AM

Answers

  • Hi There,

    Thanks for the feedback. Actually I found out that in my solution if I set the InstallShield LE project as the startup project then every time I try to run a debug session either a web app, console app, test project I get this error. Really was painful to track down and I finally notice that my solution was at times changing the startup project to be my IS LE project. Once I change the startup project away from those project types I was then able to run debugging. Even without starting the VS app over again. Note I was running VS 2010 as the Administrator.

    Thanks,

    Jake

     

    Tuesday, August 17, 2010 9:49 PM

All replies

  • 1. What kind of project are we debugging web app/windows app, etc? Is it a .NET app, C++ app, etc?
    2. Verify that you are an administrator or a member of the debugger user's group on the machine you trying to debug. After being added to the debugger users group you must log off and log back on for the settings to apply.
    3. We would need to get an ADPLUS fullonfirst crash dump AND an hang dump for devenv.exe when the error is shown.
    --Trevor H.
    Send files to Hotmail.com: "MS_TREVORH"
    Check out the Microsoft CTS TFS BLOG: blogs.msdn.com/b/dstfs
    Tuesday, August 17, 2010 9:44 PM
    Moderator
  • Hi There,

    Thanks for the feedback. Actually I found out that in my solution if I set the InstallShield LE project as the startup project then every time I try to run a debug session either a web app, console app, test project I get this error. Really was painful to track down and I finally notice that my solution was at times changing the startup project to be my IS LE project. Once I change the startup project away from those project types I was then able to run debugging. Even without starting the VS app over again. Note I was running VS 2010 as the Administrator.

    Thanks,

    Jake

     

    Tuesday, August 17, 2010 9:49 PM
  • Great! Glad it worked out, and thanks for looping back for the benefit of the community on this. :-)
    --Trevor H.
    Send files to Hotmail.com: "MS_TREVORH"
    Check out the Microsoft CTS TFS BLOG: blogs.msdn.com/b/dstfs
    Tuesday, August 17, 2010 9:53 PM
    Moderator
  • I have the same problem in several of my projects. I too am using installshield LE, and am also noticing that it changes the startup project at times. However i get this error continually, even if i manually set a different project as the startup project. I can build my code, and run without debugging fine, but when i try to debug, i get that idiotic error message.

    If i create a new sln, add all the projects from the old one, and rebuild it will work for a few days as it should (being able to debug projects), then it breaks and i cant do so any more.

    At the moment i am resorting to running the program without debugging, then attaching the debugger to the process manually as a work around, which is a rather tedious workaround. However since the error message has zero detail in it, i have no clue as to what is actually wrong.

    I have seen this behaviour on multiple computers, so am pretty sure it is not just a one off installation problem.

     

    Tuesday, December 14, 2010 1:36 PM
  • I got exactly the same problem after VS2010 with SP1 Beta crashed. I was able to debug old projects before I did complete rebuild. Now I'm getting message 'Error while trying to run project: Not Implemented' for all of them.
    Wednesday, March 9, 2011 1:15 PM
  • Hi, from my observations it seems that this is related to specific project types. For me it shows up in solutions containing InstallShield projects, and the only fix I have found is to remove the installshield project, then re-add it. This fixes things for a few builds before it screws up again. Note my problem is with the managed debugger, if you turn on mixed mode debugging it goes away (but unfortunately so does intellitrace).
    Thursday, March 10, 2011 8:29 PM
  • I unloaded the InstallShield LE project and that seems to work around the problem for the time being. 

     

    -adam


    - Adam J. Mendoza
    • Proposed as answer by Vlad Hrybok Monday, August 29, 2011 2:39 AM
    Monday, April 25, 2011 6:25 PM
  • In my case, I had a .oradbproj in my solution. After I remove(unload) this Oracle Database project, this error is gone.

    I will include this DB project back whenever I need. Still, looking for a permanent fix.

    Thanks!

    Saro


    Thanks
    Monday, January 9, 2012 10:46 AM
  • I just had the same issue. My resolution was to unload an IBM DB2 database project that was part of the solution. I also noticed that with the DB2 project active, the solution attempted to use a different project as the start up project. In this particular solution I switch between two different projects, usually compiling project #2 as a DLL, but on occasion I need to test the DLL project directly so I have a form in that project that I use as the start up object. Only when running as project #2 does the problem occur.
    Monday, June 25, 2012 3:31 PM
  • I too have noticed a similar problem.

    I recently installed VS2010SP1 and now when I set one of my projects  [C# Windows Forms Project] to be the startup project, that I get the "Error while trying to run project: Not implemented" Error when I try to debug..    If I unload the InstallShield project,  the project/solution debugs fine.   When I reload the InstallSheild project, I get the error again.   However I also found out that I must restart VS2010 before reloading the project.

    I don't have this issue with all the projects in the solution.   The main project  debugs fine.  It was just one of my 'test' projects that is not included as part of the InstallSheild installation.

    Friday, April 19, 2013 12:29 PM