open interactive window error

[Arhzi]

[Window Title]
devenv.exe

[Main Instruction]
An unexpected error occurred

[Content]
An error occurred opening this interactive window.

Please press Ctrl+C to copy the contents of this dialog and report this error to our issue tracker.

[^] Hide details [Закрыть]

[Expanded Information]

Build: 3.0.17114.1

System.TypeLoadException: Could not load type 'Microsoft.VisualStudio.InteractiveWindow.Shell.IVsInteractiveWindowFactory2' from assembly 'Microsoft.VisualStudio.VsInteractiveWindow, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
   at Microsoft.PythonTools.Repl.InteractiveWindowProvider.CreateInteractiveWindowInternal(IInteractiveEvaluator evaluator, IContentType contentType, Boolean alwaysCreate, Int32 id, String title, Guid languageServiceGuid, String replId)
   at Microsoft.PythonTools.Repl.InteractiveWindowProvider.Create(String replId, Int32 curId)
   at Microsoft.PythonTools.Repl.InteractiveWindowProvider.OpenOrCreate(String replId)
   at Microsoft.PythonTools.InterpreterList.InterpreterListToolWindow.OpenInteractiveWindow_Executed(Object sender, ExecutedRoutedEventArgs e)

[henryhchchc]

I have the same error after updated to VS2017.2

[huguesv]

Could any of you confirm the version of the Microsoft.VisualStudio.VsInteractiveWindow.dll that you have installed? It's in Common7\IDE\CommonExtensions\Microsoft\InteractiveWindow, under your VS install dir.

Additionally, what is your language setting in Tools/Options/Environment/International Settings? And what's your Windows language setting?

We're having trouble reproducing this :(

[fklier]

Same error here.

VS language setting is "English"
Windows display language setting is English (United States). Japanese and French input are also installed.
Microsoft.VisualStudio.VsInteractiveWindow.dll Product version is 2.0.0.61319 (Date Modified 2/23/2017 12:54 AM)

[henryhchchc]

I have the same dll as @huguesv do but Date Modified is May 11, Language setting is en_US, I also have Chinese IME installed.

[mwindowshz]

Save error

using version

Is there a workaround?

[huguesv]

No workaround yet, but I would hope that uninstall then reinstall would make it work again.

[mwindowshz]

Hi
Tied removing python from Visual studio , then addining it back.
did not work
Do you think uninstalling Visual Studio completely could help?

[huguesv]

That's what I would try, and I would delete the following directories before reinstalling (beware that this will wipe out your settings)
%localappdata%\Microsoft\VisualStudio\15.0*
%appdata%\Microsoft\VisualStudio\15.0*

And probably remove the C:\Program Files (x86)\Microsoft Visual Studio\2017 folder too, the installer will tell you if it's already in use when you go to reinstall.

[huguesv]

Can anyone check Event Viewer / Windows Logs / Application and see if this logs an error there that has more information than the original stack trace?

Same thing for the activity log? %AppData%\Microsoft\VisualStudio\15.0<your_id>\ActivityLog.XML

Does anyone see this error after a clean install of VS 2017? Meaning you didn't have any VS 2017 installed prior to this?

If you've updated from a previous release of VS 2017, which one was it? 15.1, 15.0 or RC from January/February? The latest RC with Python workload was 15.0.0-RC.3+26109.1 AFAIK.

I'm unable to upgrade from RC.3 to 15.2, the latest it will upgrade me to is 15.0, which doesn't have Python workload.

[huguesv]

Another thing to try is to delete the MEF cache folder.

Make sure VS is closed.
Delete %localappdata%\Microsoft\VisualStudio\15.0_<your_id>\ComponentModelCache.
Start VS. It will take longer than usual as it rebuilds the cache.

When the cache is the issue, there's usually an indication that it's the case in the error message, and there isn't any in this bug. I don't have high hopes that this will do anything, but it's easy/quick enough that it's worth trying.

[mwindowshz]

Hi Deleting MEF folder did not do anything

Inn windows log,, I am not sure this is relevant but here are some errors:

Activation context generation failed for "C:\Program Files (x86)\Windows Kits\10\bin\arm\signtool.exe.Manifest". Dependent Assembly Microsoft.Windows.Build.Appx.AppxSip.dll,version="0.0.0.0" could not be found. Please use sxstrace.exe for detailed diagnosis.

Activation context generation failed for "C:\Program Files (x86)\Windows Kits\10\bin\arm64\oleview.exe". Dependent Assembly Microsoft.Windows.Common-Controls,language="*",processorArchitecture="arm64",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0" could not be found. Please use sxstrace.exe for detailed diagnosis.

I still did not try reinstalling visual studio.

[mwindowshz]

Full uninstall and reinstall of visual studio worked
Installed 2017 professional.

[huguesv]

Thanks for reporting back @mwindowshz and sorry for the trouble.

[MikhailArkhipov]

microsoft/RTVS#3571 - customer has reliable repro

[zooba]

Has anyone had VS 2017 Preview installed at all? There may be a potential versioning issue between VS and the preview of the updates that might be at fault.

[aoime]

Yes, all machines I have that exhibit this bug had VS 2017 Preview installed when VS 2017 was upgraded to/installed.

[Funkrusha]

i had the same problem too, in my case it's the componentcache in
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\Extensions
i also had the preview installed before...

the solution:

1. remove the cached folder in C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\Extensions (search for Microsoft.VisualStudio.VsInteractiveWindow.dll in the extensions dir named above

2. restart visual studio and then vs rebuild the component cache.

maybe clean the MEF cache in %localappdata%\Microsoft\VisualStudio\15.0_<your_id>\ComponentModelCache before

[fklier]

Funkrusha's steps worked for me without needing to uninstall/reinstall anything (thanks!)

After removing the folder containing Microsoft.VisualStudio.VsInteractiveWindow.dll from the IDE\Extensions folder Visual Studio crashed on the next start. The following start rebuilt the cache and the interactive windows were opening and working normally.

[pedoc]

i had the same problem too， the following ways can solve my problem.
In particular, if you are the same as this situation:
vs version:2017 15.2 release

1.check install dirctory,if exists "Microsoft.VisualStudio.VsInteractiveWindow.dll" in "Extensions" directory(my case path:C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\Extensions\lzr5hngx.jje")
2. clean the MEF cache in %localappdata%\Microsoft\VisualStudio\15.0_<your_id>\ComponentModelCache
3.goto Common7\IDE\CommonExtensions\Microsoft\InteractiveWindow Directory copy "Microsoft.VisualStudio.InteractiveWindow.dll" and "Microsoft.VisualStudio.VsInteractiveWindow.dll" replace step 1 directory same name files.
4.restart vs

postscript：
I noticed that,in "Extensions" directory and "CommonExtensions",dll version are different,may be vs load first error dll.

hope to help

[pjwhams]

I had the same experience of fklier - I followed Funkrusha's steps and I too got the crash on the next run, but it was fine on the one after that.

[huguesv]

Looks like these upgrade issues are over now.