Site Feedback Thread

3 posts

Visual Studio Achievement plugin causes files to be locked and then our build fails

Back to Forum: Site Feedback
  • User profile image
    Solid

    We have found that the plugin causes files to become locked and that then causes the next build to fail! Anyone else seen this or have any workarounds? We are using Windows 7 64bit and Windows 2008 R2.

    The error message mentions something about open user-mapped sections!?

    Disabling or uninstalling the plugin fixes the issue. Has occurred on all our developers machines Sad

     

     

     

  • User profile image
    Maddus Mattus

    Know issue,.. They are working on it,..

  • User profile image
    jjthemachine

    I get this error on Publish only when plugin is enabled

    Application: devenv.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.InvalidOperationException
    Stack:
    at Microsoft.VisualStudio.Shell.ServiceProvider.GetService[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.Type)
    at Microsoft.VisualStudio.Shell.ActivityLog.get_Log()
    at Microsoft.VisualStudio.Shell.ActivityLog.LogEntry(Microsoft.VisualStudio.Shell.Interop.__ACTIVITYLOG_ENTRYTYPE, System.String, System.String)
    at Coding4Fun.VSAchievements.Core.VsHelper.Log(Coding4Fun.VSAchievements.Core.LogType, System.String, System.String)
    at Coding4Fun.VSAchievements.Core.VsHelper.LogError(System.String, System.String)
    at Coding4Fun.VSAchievements.SrcAchievements.SourceAnalyzer.DoAnalysis()
    at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
    at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
    at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
    at System.Threading.ThreadHelper.ThreadStart()

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.