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

비밀번호

댓글 작성자
 




... 16  17  18  19  20  [21]  22  23  24  25  26  27  28  29  30  ...
NoWriterDateCnt.TitleFile(s)
13108정성태7/26/20227480Linux: 53. container에 실행 중인 Golang 프로세스를 디버깅하는 방법 [1]
13107정성태7/25/20226684Linux: 52. Debian/Ubuntu 계열의 docker container에서 자주 설치하게 되는 명령어
13106정성태7/24/20226375오류 유형: 819. 닷넷 6 프로젝트의 "Conditional compilation symbols" 기본값 오류
13105정성태7/23/20227669.NET Framework: 2034. .NET Core/5+ 환경에서 (프로젝트가 아닌) C# 코드 파일을 입력으로 컴파일하는 방법 - 두 번째 이야기 [1]
13104정성태7/23/202210766Linux: 51. WSL - init에서 systemd로 전환하는 방법
13103정성태7/22/20227304오류 유형: 818. WSL - systemd-genie와 관련한 2가지(systemd-remount-fs.service, multipathd.socket) 에러
13102정성태7/19/20226719.NET Framework: 2033. .NET Core/5+에서는 구할 수 없는 HttpRuntime.AppDomainAppId
13101정성태7/15/202215594도서: 시작하세요! C# 10 프로그래밍
13100정성태7/15/20228082.NET Framework: 2032. C# 11 - shift 연산자 재정의에 대한 제약 완화 (Relaxing Shift Operator)
13099정성태7/14/20227960.NET Framework: 2031. C# 11 - 사용자 정의 checked 연산자파일 다운로드1
13098정성태7/13/20226180개발 환경 구성: 647. Azure - scale-out 상태의 App Service에서 특정 인스턴스에 요청을 보내는 방법 [1]
13097정성태7/12/20225574오류 유형: 817. Golang - binary.Read: invalid type int32
13096정성태7/8/20228444.NET Framework: 2030. C# 11 - UTF-8 문자열 리터럴
13095정성태7/7/20226510Windows: 208. AD 도메인에 참여하지 않은 컴퓨터에서 Kerberos 인증을 사용하는 방법
13094정성태7/6/20226264오류 유형: 816. Golang - "short write" 오류 원인
13093정성태7/5/20227139.NET Framework: 2029. C# - HttpWebRequest로 localhost 접속 시 2초 이상 지연
13092정성태7/3/20228120.NET Framework: 2028. C# - HttpWebRequest의 POST 동작 방식파일 다운로드1
13091정성태7/3/20226900.NET Framework: 2027. C# - IPv4, IPv6를 모두 지원하는 서버 소켓 생성 방법
13090정성태6/29/20226062오류 유형: 815. PyPI에 업로드한 패키지가 반영이 안 되는 경우
13089정성태6/28/20226521개발 환경 구성: 646. HOSTS 파일 변경 시 Edge 브라우저에 반영하는 방법
13088정성태6/27/20225601개발 환경 구성: 645. "Developer Command Prompt for VS 2022" 명령행 환경의 폰트를 바꾸는 방법
13087정성태6/23/20228610스크립트: 41. 파이썬 - FastAPI / uvicorn 호스팅 환경에서 asyncio 사용하는 방법 [1]
13086정성태6/22/20228039.NET Framework: 2026. C# 11 - 문자열 보간 개선 2가지파일 다운로드1
13085정성태6/22/20228113.NET Framework: 2025. C# 11 - 원시 문자열 리터럴(raw string literals)파일 다운로드1
13084정성태6/21/20226671개발 환경 구성: 644. Windows - 파이썬 2.7을 msi 설치 없이 구성하는 방법
13083정성태6/20/20227305.NET Framework: 2024. .NET 7에 도입된 GC의 메모리 해제에 대한 segment와 region의 차이점 [2]
... 16  17  18  19  20  [21]  22  23  24  25  26  27  28  29  30  ...