Microsoft MVP성태의 닷넷 이야기
글쓴 사람
정성태 (techsharer at outlook.com)
홈페이지
첨부 파일
 

Live Share 1.0.3713.0 버전을 1.0.3884.0으로 업데이트 이후 ContactServiceModelPackage 오류 발생하는 문제

오늘(2021-03-05) 기준 최신 버전인 Live Share 1.0.3884.0으로 업데이트 후 (16.9 버전의) Visual Studio 2019를 실행하면 다음과 같은 오류가 발생합니다.

The 'ContactServiceModelPackage' package did not load correctly.

The problem may have been caused by a configuration change or by the installation of another extension. You can get more information by examining the file 'C:\Users\kevin\AppData\Roaming\Microsoft\VisualStudio\16.0_d91f3cb4\ActivityLog.xml'.

Restarting Visual Studio could help resolve this issue.


그리고 xml 파일을 보면 다음과 같은 식의 오류 내용이 실려 있습니다.

SetSite failed for package [ContactServiceModelPackage]Source: 'mscorlib' Description: Could not load file or assembly 'Microsoft.VisualStudio.LiveShare, Version=1.17.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) System.IO.FileLoadException: Could not load file or assembly 'Microsoft.VisualStudio.LiveShare, Version=1.17.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) File name: 'Microsoft.VisualStudio.LiveShare, Version=1.17.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' ---> System.IO.FileLoadException: Could not load file or assembly 'Microsoft.VisualStudio.LiveShare, Version=1.16.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) File name: 'Microsoft.VisualStudio.LiveShare, Version=1.16.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].at System.Signature.GetSignature(Void* pCorSig, Int32 cCorSig, RuntimeFieldHandleInternal fieldHandle, IRuntimeMethodInfo methodHandle, RuntimeType declaringType)at System.Signature..ctor(IRuntimeMethodInfo methodHandle, RuntimeType declaringType)at System.Reflection.RuntimeConstructorInfo.get_CallingConvention()at System.Reflection.RuntimeConstructorInfo.get_InvocationFlags()at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)at Microsoft.VisualStudio.Composition.ReflectionHelpers.Instantiate(MethodBase ctorOrFactoryMethod, Object[] arguments)at Microsoft.VisualStudio.Composition.RuntimeExportProviderFactory.RuntimeExportProvider.RuntimePartLifecycleTracker.CreateValue()at Microsoft.VisualStudio.Composition.ExportProvider.PartLifecycleTracker.Create()at Microsoft.VisualStudio.Composition.ExportProvider.PartLifecycleTracker.MoveNext(PartLifecycleState nextState)at Microsoft.VisualStudio.Composition.ExportProvider.PartLifecycleTracker.MoveToState(PartLifecycleState requiredState)at Microsoft.VisualStudio.Composition.ExportProvider.PartLifecycleTracker.GetValueReadyToExpose()at Microsoft.VisualStudio.Composition.RuntimeExportProviderFactory.RuntimeExportProvider.<>c__DisplayClass15_0.<GetExportedValueHelper>b__0() --- End of stack trace from previous location where exception was thrown --- at Microsoft.VisualStudio.Composition.RuntimeExportProviderFactory.RuntimeExportProvider.<>c__DisplayClass15_0.<GetExportedValueHelper>b__0()at Microsoft.VisualStudio.Composition.RuntimeExportProviderFactory.RuntimeExportProvider.GetValueForImportElement(RuntimePartLifecycleTracker importingPartTracker, RuntimeImport import, RuntimeExport export, Func`3 lazyFactory)at Microsoft.VisualStudio.Composition.RuntimeExportProviderFactory.RuntimeExportProvider.GetValueForImportSite(RuntimePartLifecycleTracker importingPartTracker, RuntimeImport import)at Microsoft.VisualStudio.Composition.RuntimeExportProviderFactory.RuntimeExportProvider.RuntimePartLifecycleTracker.<CreateValue>b__11_0(RuntimeImport import)at System.Linq.Enumerable.WhereSelectArrayIterator`2.MoveNext()at System.Linq.Buffer`1..ctor(IEnumerable`1 source)at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)at Microsoft.VisualStudio.Composition.RuntimeExportProviderFactory.RuntimeExportProvider.RuntimePartLifecycleTracker.CreateValue()at Microsoft.VisualStudio.Composition.ExportProvider.PartLifecycleTracker.Create()at Microsoft.VisualStudio.Composition.ExportProvider.PartLifecycleTracker.MoveNext(PartLifecycleState nextState)at Microsoft.VisualStudio.Composition.ExportProvider.PartLifecycleTracker.MoveToState(PartLifecycleState requiredState)at Microsoft.VisualStudio.Composition.ExportProvider.PartLifecycleTracker.GetValueReadyToExpose()at Microsoft.VisualStudio.Composition.ExportProvider.<>c__DisplayClass63_0.<CreateExport>b__0()at Microsoft.VisualStudio.Composition.ExportProvider.<>c__DisplayClass52_3.<GetExports>b__5()at System.Lazy`1.CreateValue()at System.Lazy`1.LazyInitValue()at System.Lazy`1.get_Value()at Microsoft.VisualStudio.Composition.ExportProvider.<>c__DisplayClass80_1`2.<GetExports>b__2()at System.Lazy`1.CreateValue()at System.Lazy`1.LazyInitValue()at System.Lazy`1.get_Value()at Microsoft.VisualStudio.Composition.ExportProvider.GetExportedValue[T]()at Microsoft.VisualStudio.ComponentModelHost.ComponentModel.GetService[T]()at Microsoft.VisualStudio.Cascade.CascadePackage.<>c__DisplayClass72_0.<InitializeAsync>b__0()at System.Threading.Tasks.Task`1.InnerInvoke()at System.Threading.Tasks.Task.Execute() --- End of stack trace from previous location where exception was thrown ---at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)at Microsoft.VisualStudio.Cascade.CascadePackage.<StartHubServiceAsync>d__77.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)at Microsoft.VisualStudio.Shell.VsTaskLibraryHelper.<>c__DisplayClass35_0.<<FileAndForget>b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject) --- End of stack trace from previous location where exception was thrown --- at Microsoft.VisualStudio.Composition.ExportProvider.PartLifecycleTracker.MoveToState(PartLifecycleState requiredState)at Microsoft.VisualStudio.Composition.ExportProvider.PartLifecycleTracker.GetValueReadyToExpose()at Microsoft.VisualStudio.Composition.ExportProvider.<>c__DisplayClass63_0.<CreateExport>b__0()at Microsoft.VisualStudio.Composition.ExportProvider.<>c__DisplayClass52_3.<GetExports>b__5()at System.Lazy`1.CreateValue()at System.Lazy`1.LazyInitValue()at System.Lazy`1.get_Value()at Microsoft.VisualStudio.Composition.NetFxAdapters.MefV1ExportProvider.<>c__DisplayClass10_0.<UnwrapExport>b__1()at System.ComponentModel.Composition.Primitives.Export.GetExportedValueCore()at System.ComponentModel.Composition.Primitives.Export.get_Value()at System.ComponentModel.Composition.ReflectionModel.ImportingItem.Cast(Type type, Export export)at System.ComponentModel.Composition.ReflectionModel.ImportingItem.CastSingleExportToImportType(Type type, Export export)at System.ComponentModel.Composition.ReflectionModel.ImportingItem.CastExportsToSingleImportType(Export[] exports)at System.ComponentModel.Composition.ReflectionModel.ImportingItem.CastExportsToImportType(Export[] exports)at System.ComponentModel.Composition.ReflectionModel.ReflectionComposablePart.SetImport(ImportingItem item, Export[] exports)at System.ComponentModel.Composition.ReflectionModel.ReflectionComposablePart.SetImport(ImportDefinition definition, IEnumerable`1 exports)at System.ComponentModel.Composition.Hosting.ImportEngine.PartManager.TrySetImport(ImportDefinition import, Export[] exports)at System.ComponentModel.Composition.Hosting.ImportEngine.TrySatisfyImportSubset(PartManager partManager, IEnumerable`1 imports, AtomicComposition atomicComposition)at System.ComponentModel.Composition.Hosting.ImportEngine.TrySatisfyImportsStateMachine(PartManager partManager, ComposablePart part)at System.ComponentModel.Composition.Hosting.ImportEngine.TrySatisfyImports(PartManager partManager, ComposablePart part, Boolean shouldTrackImports)at System.ComponentModel.Composition.Hosting.ImportEngine.SatisfyImportsOnce(ComposablePart part)at System.ComponentModel.Composition.Hosting.CompositionContainer.SatisfyImportsOnce(ComposablePart part)at Microsoft.VisualStudio.Composition.NetFxAdapters.CompositionService.SatisfyImportsOnce(ComposablePart part)at System.ComponentModel.Composition.AttributedModelServices.SatisfyImportsOnce(ICompositionService compositionService, Object attributedPart)at Microsoft.VisualStudio.LiveShare.ContactServiceModel.ContactServiceModelPackage.<InitializeAsync>d__15.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)at Microsoft.VisualStudio.Shell.AsyncPackage.<>c__DisplayClass20_0.<<Microsoft-VisualStudio-Shell-Interop-IAsyncLoadablePackageInitialize-Initialize>b__1>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)at Microsoft.VisualStudio.Threading.JoinableTask.<JoinAsync>d__70.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()at Microsoft.VisualStudio.Services.VsTask.RethrowException(AggregateException e)at Microsoft.VisualStudio.Services.VsTask.InternalGetResult(Boolean ignoreUIThreadCheck)at Microsoft.VisualStudio.Services.VsTask.GetResult() System.IO.FileLoadException: Could not load file or assembly 'Microsoft.VisualStudio.LiveShare, Version=1.16.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) File name: 'Microsoft.VisualStudio.LiveShare, Version=1.16.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].


오류 메시지에 따라 분명히 Microsoft.VisualStudio.LiveShare.dll 로딩에 문제가 있어 보입니다. 1.17.0.0 버전과 1.16.0.0 버전을 함께 찾고 있는데, 실제로 시스템에 설치된 모듈을 찾아 보면,

// C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\Extensions\Microsoft\LiveShare\Microsoft.VisualStudio.LiveShare.dll
// Microsoft.VisualStudio.LiveShare, Version=1.18.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a

1.18.0.0 버전입니다. 게다가 해당 모듈이 참조하는 DLL은 다음과 같이 기본 모듈이므로,

  • mscorlib
  • System
  • System.ComponentModel.Composition
  • System.Core
  • System.Runtime.Serialization

"Could not load file or assembly ... one of its dependencies" 오류 메시지에서 로딩 실패가 된 것은 다름 아닌 바로 그 모듈에 문제가 있어 보입니다.

게다가 이런 상태에서 비주얼 스튜디오의 "Live Share" 버튼을 누르면 다음과 같은 오류 메시지가 발생합니다.

Failed to create a collaboration session. Could not load file or assembly 'Microsoft.VisualStudio.LiveShare, Version=1.17.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)





업그레이드 절차가 매끄럽지 못한 것인지는 알 수 없으나 일단 이런 경우에는 bindingRedirect를 이용해야만 할 것 같습니다.

.NET Framework의 Strong-named 어셈블리 바인딩 (1) - app.config을 이용한 바인딩 리디렉션
; https://www.sysnet.pe.kr/2/0/12210

따라서 비주얼 스튜디오의 실행 모듈인 devenv.exe의 config 파일을 찾아서,

C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\devenv.exe.config

LiveShare 모듈을 확인했더니 오류가 날 만한 설정 상태였습니다.

...[생략]...

<!-- Live Share API -->
<dependentAssembly>
    <assemblyIdentity name="Microsoft.VisualStudio.LiveShare" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
    <bindingRedirect oldVersion="0.0.0.0-1.16.0.0" newVersion="1.16.0.0"/>
    <codeBase version="1.16.0.0" href="Extensions\Microsoft\LiveShareApi\Microsoft.VisualStudio.LiveShare.dll"/>
</dependentAssembly>

...[생략]...

문제 해결을 위해, 1.18.0.0 버전이 사용되어야 하므로 다음과 같이 바꾸거나,

<!-- Live Share API -->
<dependentAssembly>
    <assemblyIdentity name="Microsoft.VisualStudio.LiveShare" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
    <bindingRedirect oldVersion="0.0.0.0-1.18.0.0" newVersion="1.18.0.0"/>
    <codeBase version="1.16.0.0" href="Extensions\Microsoft\LiveShareApi\Microsoft.VisualStudio.LiveShare.dll"/>
</dependentAssembly>

아니면 아예 Microsoft.VisualStudio.LiveShare 항목 자체를 삭제해 버리면 됩니다. (아마도 삭제하면 저 설정이 필요한 환경 구성인 경우 오류가 발생할 것이고, 삭제하지 않으면 향후에도 LiveShare 모듈이 1.19.0.0 버전으로 올라갔을 때 다시 저 파일을 수정해야 할 것입니다. 저는 어느 쪽이 될지 테스트하기 위해 ^^ PC 한 대는 1.18.0.0으로 바꾸고 나머지 한 대는 삭제를 해두었습니다.)

이렇게 보면, 왠지 업그레이드 절차에 문제가 있는 것이 맞는 듯합니다. ^^ 어쨌든 저렇게 변경하고 다시 비주얼 스튜디오를 실행하면 이후 ContactServiceModelPackage 오류 메시지 상자도 안 뜨고 Live Share 기능도 잘 동작합니다.




[이 글에 대해서 여러분들과 의견을 공유하고 싶습니다. 틀리거나 미흡한 부분 또는 의문 사항이 있으시면 언제든 댓글 남겨주십시오.]







[최초 등록일: ]
[최종 수정일: 3/5/2021]

Creative Commons License
이 저작물은 크리에이티브 커먼즈 코리아 저작자표시-비영리-변경금지 2.0 대한민국 라이센스에 따라 이용하실 수 있습니다.
by SeongTae Jeong, mailto:techsharer at outlook.com

비밀번호

댓글 작성자
 




... [121]  122  123  124  125  126  127  128  129  130  131  132  133  134  135  ...
NoWriterDateCnt.TitleFile(s)
10900정성태2/19/201622195.NET Framework: 548. Linq는 결국 메서드 호출! [3]파일 다운로드1
10899정성태2/17/201623498개발 환경 구성: 282. kernel32.dll, kernel32legacy.dll, api-ms-win-core-sysinfo-l1-2-0.dll [1]
10898정성태2/17/201622013.NET Framework: 547. PerformanceCounter의 InstanceName 지정 시 주의 사항파일 다운로드1
10897정성태2/17/201621292디버깅 기술: 76. windbg 분석 사례 - 닷넷 프로파일러의 GC 콜백 부하
10896정성태2/17/201622388오류 유형: 320. FATAL: 28000: no pg_hba.conf entry for host "fe80::1970:8120:695:a41e%12"
10895정성태2/17/201621273.NET Framework: 546. System.AppDomain으로부터 .NET Profiler의 AppDomainID 구하는 방법 [1]
10894정성태2/17/201621994오류 유형: 319. Visual Studio에서 찾기는 성공하지만 해당 소스 코드 정보가 보이지 않는 경우
10893정성태2/16/201620629.NET Framework: 545. 닷넷 - 특정 클래스가 로드되었는지 여부를 알 수 있을까? - 두 번째 이야기
10892정성태2/16/201621248오류 유형: 318. 탐색기에서 폴더 생성/삭제 시 몇 초 동안 멈추는 현상
10891정성태2/16/201624286VC++: 95. 내 CPU가 MPX/SGX를 지원할까요? [1]
10890정성태2/15/201624091.NET Framework: 544. C# 5의 Caller Info를 .NET 4.5 미만의 응용 프로그램에 적용하는 방법 [5]
10889정성태2/14/201620435.NET Framework: 543. C++의 inline asm 사용을 .NET으로 포팅하는 방법 - 두 번째 이야기파일 다운로드1
10888정성태2/14/201618736.NET Framework: 542. 닷넷 - 특정 클래스가 로드되었는지 여부를 알 수 있을까?
10887정성태2/3/201619441VC++: 94. MPX(Memory Protection Extensions) 테스트파일 다운로드1
10886정성태2/3/201620684개발 환경 구성: 281. Intel MPX Runtime Driver 수동 설치
10885정성태2/2/201620374오류 유형: 317. Sybase.Data.AseClient.AseException: The command has timed out.
10884정성태1/11/201621619개발 환경 구성: 280. 닷넷에서 SAP Adaptive Server Enterprise 데이터베이스 사용파일 다운로드1
10882정성태1/6/201620907Windows: 113. 윈도우의 2179, 26143, 47001 TCP 포트 사용 [1]
10881정성태1/3/201622338오류 유형: 316. 윈도우 10 - 바탕/돋음 체가 사라져 한글이 깨지는 현상 [2]
10880정성태12/16/201520026오류 유형: 315. 닷넷 프로파일러의 오류 코드 정보
10879정성태12/16/201521969오류 유형: 314. Error : DEP0700 : Registration of the app failed. error 0x80070005
10878정성태12/9/201525135디버깅 기술: 75. UWP(유니버설 윈도우 플랫폼) 앱에서 global::System.Diagnostics.Debugger.Break 예외 발생 시 대응 방법
10877정성태12/9/201529482VC++: 93. std::thread 사용 시 R6010 오류 [2]
10876정성태11/26/201525520.NET Framework: 541. SignedXml을 이용한 ds:Signature만드는 방법 [3]파일 다운로드1
10875정성태11/26/201530522개발 환경 구성: 279. signtool.exe의 다중 서명 기능 [2]
10874정성태11/26/201526489개발 환경 구성: 278. 인증서와 인증서를 이용한 코드 사인의 해시 구분
... [121]  122  123  124  125  126  127  128  129  130  131  132  133  134  135  ...