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

비밀번호

댓글 작성자
 




... 76  77  78  79  80  81  [82]  83  84  85  86  87  88  89  90  ...
NoWriterDateCnt.TitleFile(s)
11921정성태5/28/201926201Math: 55. C# - 다항식을 위한 최소 자승법(Least Squares Method)파일 다운로드1
11920정성태5/28/201916870.NET Framework: 839. C# - PLplot 색상 제어
11919정성태5/27/201922155Math: 54. C# - 최소 자승법의 1차 함수에 대한 매개변수를 단순 for 문으로 구하는 방법 [1]파일 다운로드1
11918정성태5/25/201922052Math: 53. C# - 행렬식을 이용한 최소 자승법(LSM: Least Square Method)파일 다운로드1
11917정성태5/24/201923478Math: 52. MathNet을 이용한 간단한 통계 정보 처리 - 분산/표준편차파일 다운로드1
11916정성태5/24/201921477Math: 51. MathNET + OxyPlot을 이용한 간단한 통계 정보 처리 - Histogram파일 다운로드1
11915정성태5/24/201924967Linux: 11. 리눅스의 환경 변수 관련 함수 정리 - putenv, setenv, unsetenv
11914정성태5/24/201923664Linux: 10. 윈도우의 GetTickCount와 리눅스의 clock_gettime파일 다운로드1
11913정성태5/23/201919548.NET Framework: 838. C# - 숫자형 타입의 bit(2진) 문자열, 16진수 문자열 구하는 방법파일 다운로드1
11912정성태5/23/201920150VS.NET IDE: 137. Visual Studio 2019 버전 16.1부터 리눅스 C/C++ 프로젝트에 추가된 WSL 지원
11911정성태5/23/201919327VS.NET IDE: 136. Visual Studio 2019 - 리눅스 C/C++ 프로젝트에 인텔리센스가 동작하지 않는 경우
11910정성태5/23/201928068Math: 50. C# - MathNet.Numerics의 Matrix(행렬) 연산 [1]파일 다운로드1
11909정성태5/22/201922888.NET Framework: 837. C# - PLplot 사용 예제 [1]파일 다운로드1
11908정성태5/22/201921721.NET Framework: 836. C# - Python range 함수 구현파일 다운로드1
11907정성태5/22/201918207오류 유형: 541. msbuild - MSB4024 The imported project file "...targets" could not be loaded
11906정성태5/21/201918557.NET Framework: 835. .NET Core/C# - 리눅스 syslog에 로그 남기는 방법
11905정성태5/21/201918849.NET Framework: 834. C# - 폴더 경로 문자열에서 "..", "." 표기를 고려한 최종 문자열을 얻는 방법 - 두 번째 이야기
11904정성태5/21/201927773.NET Framework: 833. C# - Open Hardware Monitor를 이용한 CPU 온도 정보 [1]파일 다운로드1
11903정성태5/21/201921499오류 유형: 540. .NET Core - System.PlatformNotSupportedException: The named version of this synchronization primitive is not supported on this platform.
11902정성태5/21/201919075오류 유형: 539. mstest 실행 시 "The directory name is invalid." 오류 발생
11901정성태5/21/201921572오류 유형: 538. msbuild 오류 - Could not find a part of the path '%LOCALAPPDATA%\Temp\2\.NETFramework,Version=v4.0.AssemblyAttributes.cs'
11900정성태5/18/201920420오류 유형: 537. "sfc /scannow" 실행 중 시스템이 부팅되는 현상
11899정성태5/17/201921161Linux: 9. Linux에서 윈도우의 OutputDebugString 대신 사용할 수 있는 syslog [1]
11898정성태5/16/201922743VC++: 130. C++ string의 c_str과 data 함수의 차이점 [3]
11897정성태5/16/201929301오류 유형: 536. Visual Studio - "Developer Pack"을 설치했는데도 "대상 프레임워크" 목록에 나오지 않는 경우 [2]
11896정성태5/15/201925126개발 환경 구성: 440. C#, C++ - double의 Infinity, NaN 표현 방식파일 다운로드1
... 76  77  78  79  80  81  [82]  83  84  85  86  87  88  89  90  ...