Tech Off Thread

13 posts

A problem with VS Achievements

Back to Forum: Tech Off
  • User profile image
    RodAtWork

    I believe there's a problem with the new Visual Studio Achievements for VS 2010.  I've been getting fatal errors trying to debug changes I've made to a WPF app.  I've detailed the errors on MSDN Social.

  • User profile image
    karstenj

    Thanks for letting us know. We've logged the bug and are currently investigating. We've got another known issue about FxCop locking files, which this may be related to.

  • User profile image
    Danimar

    I also getting a problem, that I think is related to Visual Studio Achievements.

    Every time, I start debugging my web app, visual studio crashes and needs to restart.

    The file 'C:\Users\Danimar\AppData\Local\Temp\wus2bvrd.pe0\SysGestao\bin\Antlr3.Runtime.dll' already exists.
    
       at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
       at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite)
       at System.IO.File.Copy(String sourceFileName, String destFileName)
       at Coding4Fun.VSAchievements.FxCopAchievements.FxCopManager.CopyDirectory(String sourceDir, String destDir)
       at Coding4Fun.VSAchievements.FxCopAchievements.FxCopManager.GetTempAssemblies(String tempDir)
       at Coding4Fun.VSAchievements.FxCopAchievements.FxCopManager.RunFxCop()
       at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()

     

    I hope this help to find the problem.

  • User profile image
    harlock123

    My Development environment started getting all wonky and had to turn off the Achievements Extension. With it on, VS crashed on every build after the build was complete. With it off, no problems. I was building a Silverlight application hosted on a local version of IIS running in my dev machine. 

    I had recently updated the extension twice and it got progressively worse and worse. With it off, the system is running well again..

  • User profile image
    kipusoep

    I've got exactly the same problem, really annoying...

  • User profile image
    timgaunt

    I'm getting this too, I don't know if it helps debug the issue but I've noticed it mainly happens on projects which have multiple projects outputting to the same folder which would tie in with your thoughts on locking files.

    HTH

    Tim

  • User profile image
    vdimov

    Same error here.

  • User profile image
    harlock123

    Well my personal opinion is the thing a not worth the time to troubleshoot on what should be a 'No Brainer'. Its off and stability has returned, simple as that....

     

  • User profile image
    Bemko

    I have similar problem with VS Achievements. In my case VS2010 crashes every time I try to build any C++ project, even console HelloWorld. No problems with C# though. I believe that it is connected with FxCop, beacause if I disable it in Achievements options everything works fine. I have previously installed FxCop 1.36, but now I've updated it to 10.0 and I still have the same problem.

    Stack trace from debugging devenv.exe:

    >    System.Core.dll!System.Linq.Enumerable.First<System.Tuple<string,string>>(System.Collections.Generic.IEnumerable<System.Tuple<string,string>> source) + 0x151 bytes    
        Coding4Fun.VSAchievements.FxCopAchievements.dll!Coding4Fun.VSAchievements.FxCopAchievements.FxCopManager.LongestCommonRoot(System.Collections.Generic.List<System.Tuple<string,string>> paths) + 0x2e bytes    
        Coding4Fun.VSAchievements.FxCopAchievements.dll!Coding4Fun.VSAchievements.FxCopAchievements.FxCopManager.GetTempAssemblies(string tempDir) + 0x5a bytes    
        Coding4Fun.VSAchievements.FxCopAchievements.dll!Coding4Fun.VSAchievements.FxCopAchievements.FxCopManager.RunFxCop() + 0x101 bytes    
        mscorlib.dll!System.Threading.ThreadHelper.ThreadStart_Context(object state) + 0x63 bytes    
        mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state, bool ignoreSyncCtx) + 0xb0 bytes    
        mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) + 0x2c bytes    
        mscorlib.dll!System.Threading.ThreadHelper.ThreadStart() + 0x44 bytes    
        [Native to Managed Transition]    
    

  • User profile image
    karstenj

    Hi All -- We just pushed out a new build (version 1.6) that should fix this issue. Another option is to completely disable FxCop, but still keep the extension installed, which is an option now under Tools/Options/VSAchievements

  • User profile image
    harlock123

    Well New build or no... I updated to the newest build. My Silverlight projects that are hosted on an IIS server in my test system still fail to start-up in debug until I turn off the extension. So off it will remain....

  • User profile image
    harlock123

    Just updated to the newest Version 1.7 of this addon.

    Clean reboot, plugin enabled, loaded project and ensured my normal debug setting were enabled (Historically I have had to turn off ASP.NET debugging with this plugin) Well it still is giving me fits. With the add on disabled all is normal. If I turn it on and build It and run it Hangs the dev environment for like 2 minutes or so and gives me the the WEB SERVER IS NOT RESPONDING IN A TIMELY MANNER... While its hung I can open a browser and point at localhost/{myslapp} and it comes up just fine....

    So for now it remains disabled....

     

  • User profile image
    karstenj

    Thanks for reporting. We've logged the bug and will investigate.

Comments closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.