Ptvs: MSVS 2015 Update 3 does not work with PTVS

Created on 29 Jun 2016 · 5Comments · Source: microsoft/PTVS

Python tools seems to be broken. It’s still showing 2.2.3 is currently installed and update 2.2.4 is availiable. But during installation “Update” button is gray that makes update not possible

Source

ehoeks

Most helpful comment

This is an occasional upgrade issue that we haven't been able to track down. VS keeps a cache of loaded assemblies that doesn't always get invalidated when it should.

If you delete C:\Users\You\AppData\Local\Microsoft\VisualStudio\14.0\ComponentModelCache and restart you should be fine.

zooba on 30 Jun 2016

👍5

All 5 comments

We accidentally published a release with the wrong version number in Extensions and Updates. This triggers the notification, even though you've got 2.2.4 installed (see Help/About).

It was republished last week with the fix - before it went public - but it seems people are still getting the earlier version somehow (probably a CDN issue). If you install the 2.2.4 release from the releases page you'll get the version number fix and won't see the notification any more.

(Uninstalling and reinstalling through the VS installer does not work because of the caching done by the installer.)

zooba on 29 Jun 2016

😕1

Thank you for the very fast reaction. This kind of slip-ups can happen to anybody.

But, after the install of 2.2.4 from the release page I still have an error loading the plugin.

error

398
2016/06/30 06:13:29.265
Error
VisualStudio
LegacySitePackage failed for package [Python Tools Package]Source: 'Microsoft.VisualStudio.Composition' Description: Expected 1 export(s) with contract name "Microsoft.PythonTools.Interpreter.IInterpreterOptionsService" but found 0 after applying applicable constraints. Microsoft.VisualStudio.Composition.CompositionFailedException: Expected 1 export(s) with contract name "Microsoft.PythonTools.Interpreter.IInterpreterOptionsService" but found 0 after applying applicable constraints. at Microsoft.VisualStudio.Composition.ExportProvider.GetExports(ImportDefinition importDefinition) at Microsoft.VisualStudio.Composition.ExportProvider.GetExportsT,TMetadataView at Microsoft.VisualStudio.Composition.ExportProvider.GetExportT,TMetadataView at Microsoft.VisualStudio.Composition.ExportProvider.GetExportT at Microsoft.VisualStudio.Composition.ExportProvider.GetExportT at Microsoft.VisualStudio.Composition.ExportProvider.GetExportedValueT at Microsoft.VisualStudio.ComponentModelHost.ComponentModel.GetServiceT at Microsoft.PythonTools.PythonToolsService..ctor(IServiceContainer container) at Microsoft.PythonTools.PythonToolsPackage.Initialize() at Microsoft.VisualStudio.Shell.Package.Microsoft.VisualStudio.Shell.Interop.IVsPackage.SetSite(IServiceProvider sp)
{6DBD7C1E-1F1B-496D-AC7C-C55DAE66C783}

80131500

399
2016/06/30 06:13:29.280
Error
VisualStudio
SetSite failed for package Python Tools Package
{6DBD7C1E-1F1B-496D-AC7C-C55DAE66C783}

80131500

400
2016/06/30 06:13:29.282
Error
VisualStudio
End package load [Python Tools Package]
{6DBD7C1E-1F1B-496D-AC7C-C55DAE66C783}

80131500

ehoeks on 30 Jun 2016

This is an occasional upgrade issue that we haven't been able to track down. VS keeps a cache of loaded assemblies that doesn't always get invalidated when it should.

If you delete C:\Users\You\AppData\Local\Microsoft\VisualStudio\14.0\ComponentModelCache and restart you should be fine.

zooba on 30 Jun 2016

👍5

@zooba FYI RTVS added setup custom action to wipe that folder, as a workaround to that occasional bug.
https://github.com/Microsoft/RTVS/blob/master/src/SetupCustomActions/CustomAction.cs#L66