Visual Studio 2019 Install Failing #84

ToddTaylor · 2018-12-27T20:37:16Z

When attempting to install the Object Exporter in Visual Studio 2019 (16.0.0 Preview 1.1), an error occurs with the following message:

12/27/2018 2:32:30 PM - Extension cannot be installed to the following products due to missing prerequisites: 12/27/2018 2:32:30 PM - Microsoft Visual Studio Enterprise 2019 12/27/2018 2:32:30 PM - ------------------------------------------------------- 12/27/2018 2:32:30 PM - Identifier : Microsoft.VisualStudio.Component.CoreEditor 12/27/2018 2:32:30 PM - Name : Visual Studio core editor 12/27/2018 2:32:30 PM - Version : [11.0,16.0) 12/27/2018 2:32:30 PM - Error : The prerequisite version specified does not match the version installed 12/27/2018 2:32:30 PM - 12/27/2018 2:32:30 PM - System.InvalidOperationException: No modifications could be applied.

The text was updated successfully, but these errors were encountered:

ToddTaylor · 2019-02-07T19:21:19Z

The fix is very simple... just some minor tweaks to the .vsixmanifest:

https://blogs.msdn.microsoft.com/visualstudio/2018/09/26/how-to-upgrade-extensions-to-support-visual-studio-2019/

robalexclark · 2019-03-25T12:56:38Z

Hi - can you please provide an updated build for 2019 as I tried the fixes suggested but couldn't get it to compile.

OmarElabd · 2019-03-25T17:57:27Z

I will try and provide a 2019 build in the next couple of weeks.

dharmaturtle · 2019-04-30T00:52:50Z

Dunno if this is in bad taste, but in the meantime I've been using this, which works at runtime instead of being a plugin.

https://www.nuget.org/packages/ObjectDumper.NET/

ibyet05 · 2019-05-01T13:18:48Z

It is not enough to change .vsixmanifest only. You should do same things for catalog.json as well.

mzhukovs · 2019-05-15T03:01:33Z

I can't install for VS2019 either:

keyle56 · 2019-06-25T16:38:08Z

Hi! Is there any update on when the extension will work "out of the box"?

sehuff · 2019-07-04T03:05:50Z

The fix is very simple... just some minor tweaks to the .vsixmanifest:

https://blogs.msdn.microsoft.com/visualstudio/2018/09/26/how-to-upgrade-extensions-to-support-visual-studio-2019/

I updated the file - but it appears I need a license to Telerik.WinControls.dll in order to do the build?

sehuff · 2019-07-04T03:26:56Z

Nevermind my last comment I just had to unblock the downloaded files before the build. However, I know have the same issue as mzhukovs - prerequisites that cannot be resolved.

domusvita-zz · 2019-08-15T17:48:22Z

Looks like a pull request has been pending for a little over a week that might fix this issue. Hopefully gets merged soon. Looks like a great product.

maxcl10 · 2019-10-01T09:24:33Z

Is there any news on this topic. When installing the extension only vs2017 is proposed.

vurso · 2019-10-09T14:45:29Z

Is this fixed? I tried the latest version and sadly it doesn't work in VS2019 such a shame

ldy985 · 2019-10-09T18:50:27Z

I compiled a version using one of the pull requests:
ObjectExporter.zip it should work fine with VS2019.

krs4444 · 2019-10-31T08:46:38Z

I compiled a version using one of the pull requests:
ObjectExporter.zip it should work fine with VS2019.

Thank you, this one works on VS2019 Community Edition too!

vurso · 2020-02-16T22:43:20Z

I compiled a version using one of the pull requests:
ObjectExporter.zip it should work fine with VS2019.

Thank you, this one works on VS2019 Community Edition too!

Someone should fork this project (with the fixed version).

SteGriff · 2020-03-05T15:36:34Z

Instead of rebuilding, you can also hack the vsix:

Change the extension from vsix to zip, and unzip it
In both manifest.json and catalog.json find CoreEditor and replace that key-value pair with "Microsoft.VisualStudio.Component.CoreEditor":"[15.0,17.0)"
In extension.vsixmanifest replace the content of the Installation XML node with:

    <InstallationTarget Version="[14.0,17.0)" Id="Microsoft.VisualStudio.Community" />
    <InstallationTarget Version="[14.0,17.0)" Id="Microsoft.VisualStudio.Pro" />
    <InstallationTarget Version="[14.0,17.0)" Id="Microsoft.VisualStudio.Enterprise" />

Hope it helps someone :)

breadshort · 2020-03-09T19:48:15Z

Still can't install the extension:
error "This extension is not installable on any currently installed products."
Installation log:

09.03.2020 22:45:04 - Microsoft VSIX Installer
09.03.2020 22:45:04 - -------------------------------------------
09.03.2020 22:45:04 - Initializing Install...
09.03.2020 22:45:04 - Extension Details...
09.03.2020 22:45:04 - 	Identifier      : 07fb5b16-f4be-4488-9a19-b4f36d2c05a6
09.03.2020 22:45:04 - 	Name            : Object Exporter
09.03.2020 22:45:04 - 	Author          : Omar Elabd
09.03.2020 22:45:04 - 	Version         : 1.8.0
09.03.2020 22:45:04 - 	Description     : Object Exporter creates serializations of in memory objects from your various debugging windows. Currently supported output formats are: CSharp Object Initialization Code, JSON and XML.
09.03.2020 22:45:04 - 	Locale          : en-US
09.03.2020 22:45:04 - 	MoreInfoURL     : http://www.omarelabd.net/exporting-objects-from-the-visual-studio-debugger/
09.03.2020 22:45:04 - 	InstalledByMSI  : False
09.03.2020 22:45:04 - 	SupportedFrameworkVersionRange : [4.5,)
09.03.2020 22:45:04 - 
09.03.2020 22:45:04 - 	Supported Products : 
09.03.2020 22:45:04 - 		Microsoft.VisualStudio.Community
09.03.2020 22:45:04 - 			Version : [14.0,17.0)
09.03.2020 22:45:04 - 		Microsoft.VisualStudio.Pro
09.03.2020 22:45:04 - 			Version : [14.0,17.0)
09.03.2020 22:45:04 - 		Microsoft.VisualStudio.Enterprise
09.03.2020 22:45:04 - 			Version : [14.0,17.0)
09.03.2020 22:45:04 - 
09.03.2020 22:45:04 - 	References      : 
09.03.2020 22:45:04 - 
09.03.2020 22:45:04 - Searching for applicable products...
09.03.2020 22:45:04 - Found installed product - Global Location
09.03.2020 22:45:04 - Found installed product - AtmelStudio
09.03.2020 22:45:04 - VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products.
   at VSIXInstaller.App.InitializeInstall(Boolean isRepairSupported)
   at VSIXInstaller.App.InitializeInstall()
   at System.Threading.Tasks.Task.InnerInvoke()
   at System.Threading.Tasks.Task.Execute()

SteGriff · 2020-03-10T15:36:24Z

Still can't install the extension:
error "This extension is not installable on any currently installed products."
Installation log:
snip

@breadshort, what version and edition of VS are you installing it into? Add the version numbers and editions to manifest.json, catalog.json, and extension.vsixmanifest, as described above.

breadshort · 2020-03-10T16:03:17Z

@breadshort, what version and edition of VS are you installing it into? Add the version numbers and editions to manifest.json, catalog.json, and extension.vsixmanifest, as described above.

2017 Enterprise 15.9.20 (trial)
2019 Community 16.4.5
2019 Pro 16.4.5 (trial)
2019 Enterprise 16.4.5 (trial)

I did everything that @SteGriff described (see attached file ObjectExporter.zip
)
still can't install the extension (same error)

UPD: I think that some people don't work on my VS - I can't install the Microsoft Code Analysis extension either. I'll find out why.

UPD2: Solved. The problem was because of the wrong version of vsixinstaller.exe.

x123-design · 2020-03-13T12:03:10Z

@SteGriff thanks for the tips but I double click the ObjectExplorer.vsix file I get:

Microsoft.VisualStudio.ExtensionManager.MissingPackagePartException: This VSIX package is invalid because it does not contain the file extension.vsixmanifest at the root. The VSIX file may be corrupted.

The extension.vsixmanifest file is there though.

After doing the edits you suggest, I zip the folder, I rename to ObjectExplorer.vsix

Thanks

breadshort · 2020-03-13T12:10:19Z

@gustier

After doing the edits you suggest, I zip the folder, I rename to ObjectExplorer.vsix

You should not archive a folder, but the contents of a folder.

x123-design · 2020-03-13T12:23:22Z

@breadshort
Ah, right, makes sense.
I dragged them out of the zip and edited and dragged back - seemed to install ok
Thanks

x123-design · 2020-03-13T12:37:45Z

@breadshort
Ok, I have checked the extension is enabled which it is.
However, when I hit a breakpoint I expect to see the 'Export Objects' in the menu.
Any ideas how to get the exporter window?

x123-design · 2020-03-13T12:53:56Z

@breadshort - in VS 2019

breadshort · 2020-03-13T13:13:07Z

@gustier

Any ideas how to get the exporter window?

Main menu -> Tools -> Export Objects

x123-design · 2020-03-13T14:28:47Z

@breadshort
Yes, been using ctrl+E, ctrl+O, as no menu in VS 2019.

The Object Exporter is proving very buggy.

@anyone, Is there a commercial product that does this which supports newer versions of .net?

SteGriff · 2020-03-13T14:30:48Z

As mentioned earlier in the thread, it's worth looking at ObjectDumper.NET, I found its output to be better, but you do need to write some code (not very difficult): https://www.nuget.org/packages/ObjectDumper.NET/

x123-design · 2020-03-13T14:34:52Z

Nice, Thanks

bigloudjeff · 2020-03-13T14:59:42Z

I am not affiliated with this product in any way other than being a customer. But I find OzCode to be useful and it has an almost identical object exporting feature.
https://oz-code.com/debugging-redefined/

dharmaturtle · 2020-03-13T16:22:19Z

I actually prefer ObjectDumper.net these days because I use a program called NCrunch that makes it simple to see the console output of tests. I have an extension method .D() that takes the object it's attached to and feeds it to ObjectDumper.net, which then prints it to the console. Makes me want to write tests now, as compared to being forced to do it. Unfortunately, NCrunch is not free, nor am I aware of another program/plugin that makes it simple to see a test's console output.

I made a small repo here that demonstrates how you can "dump" the console to a file. When combined with an autoupdating text editor like VS Code, the experience is somewhat better. Somewhat =\ If someone could figure out how to execute the "Repeat last run" command twice in a row, that would be great.

Edit: Aaaand I figured it out. To execute "Repeat last run" repeatedly, make a change in your code, save, and then try to run it again. I guess VS is trying to save you from running the same test over and over.

tahir-khalid · 2020-10-09T15:38:10Z

I am not affiliated with this product in any way other than being a customer. But I find OzCode to be useful and it has an almost identical object exporting feature.
https://oz-code.com/debugging-redefined/

Nice tool reminds me of CodeRush which I use and love.

vurso · 2020-10-16T15:51:41Z

Looks like the author abandoned the project so I will try and pick this up with my own fork.

OmarElabd · 2020-10-16T18:43:12Z

@vurso I just want to clarify that the project hasn't been abandoned and there are updates planned for the near future.

vurso · 2020-10-16T23:11:29Z

@vurso I just want to clarify that the project hasn't been abandoned and there are updates planned for the near future.

Great to hear you're still here Omar look forward to the updates my friend. Be safe and well. Peace

igoyetche · 2020-11-10T14:29:25Z

Please update it for VS2019

redwards510 · 2020-12-02T19:25:03Z

I did the fixes suggested by @SteGriff but I still get the "dependencies cannot be resolved" error when trying to install. this is VS 2019 Pro. Hoping for a fix because Ozcode costs money!

vurso · 2020-12-02T19:47:05Z

Would be good to compile a list of current issues. Personally I think my issues are to do with the version of Visual Studio 2019 in my case its Enterprise on Windows 10 LTSB so location of extensions for example is completely not what you expect so I think once we work out where stuff should go and someone fixes the installer should have a better chance of working maybe?

…

On Wed, 2 Dec 2020 at 19:25, Ryan E ***@***.***> wrote: I did the fixes suggested by @SteGriff <https://github.com/SteGriff> but I still get the "dependencies cannot be resolved" error when trying to install. this is VS 2019 Pro. Hoping for a fix because Ozcode costs money! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#84 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHTRHH6OEZUHHLFPIGUXJTSS2IB5ANCNFSM4GMMVZMA> .

ldy985 · 2020-12-02T21:16:58Z

Have you tried the version I compiled a long time ago? #84 (comment)

vreniose95 · 2022-04-29T18:18:54Z

I compiled a version using one of the pull requests: ObjectExporter.zip it should work fine with VS2019.

Thanks a ton my man!
King

stefan-sherwood · 2023-01-11T21:18:38Z

Note that the instructions on how to modify the extension to work in VS2019 left out another place to edit:

From extension.vsixmanifest:

  <Prerequisites>
    <Prerequisite Id="Microsoft.VisualStudio.Component.CoreEditor" Version="[14.0,17.0)" DisplayName="Visual Studio core editor" />
  </Prerequisites>

needs to be changed to

  <Prerequisites>
    <Prerequisite Id="Microsoft.VisualStudio.Component.CoreEditor" Version="[15.0,17.0)" DisplayName="Visual Studio core editor" />
  </Prerequisites>

When I followed the linked instructions using version [17.0,18.0) in all 3 places (catalog.json, manifest.json, extension.vsixmanifest) and also changed:

<Installation InstalledByMsi="false">
  <InstallationTarget Id="Microsoft.VisualStudio.Pro" Version="[14.0,17.0)" />
</Installation>

to

  <Installation InstalledByMsi="false">
    <InstallationTarget Id="Microsoft.VisualStudio.Community" Version="[15.0,17.0)">
       <ProductArchitecture>x86</ProductArchitecture>
    </InstallationTarget>
    <InstallationTarget Id="Microsoft.VisualStudio.Community" Version="[17.0,18.0)">
       <ProductArchitecture>amd64</ProductArchitecture>
    </InstallationTarget>
  </Installation>

in extension.vsixmanifest, I was able to get it to install in Visual Studio 2022. But when I run the extension I'm greeted with this message:

OmarElabd self-assigned this Mar 25, 2019

OmarElabd added the feature label Mar 25, 2019

vzilinas mentioned this issue Apr 19, 2019

Updated .vsixmanifest to work on VS 2019 #86

Closed

Visual Studio 2019 Install Failing #84

Visual Studio 2019 Install Failing #84

Comments

ToddTaylor commented Dec 27, 2018

ToddTaylor commented Feb 7, 2019

robalexclark commented Mar 25, 2019

OmarElabd commented Mar 25, 2019

dharmaturtle commented Apr 30, 2019

ibyet05 commented May 1, 2019

mzhukovs commented May 15, 2019

keyle56 commented Jun 25, 2019

sehuff commented Jul 4, 2019

sehuff commented Jul 4, 2019

domusvita-zz commented Aug 15, 2019

maxcl10 commented Oct 1, 2019

vurso commented Oct 9, 2019

ldy985 commented Oct 9, 2019

krs4444 commented Oct 31, 2019

vurso commented Feb 16, 2020

SteGriff commented Mar 5, 2020 • edited

breadshort commented Mar 9, 2020

SteGriff commented Mar 10, 2020

breadshort commented Mar 10, 2020 • edited

x123-design commented Mar 13, 2020

breadshort commented Mar 13, 2020

x123-design commented Mar 13, 2020

x123-design commented Mar 13, 2020

x123-design commented Mar 13, 2020

breadshort commented Mar 13, 2020

x123-design commented Mar 13, 2020

SteGriff commented Mar 13, 2020

x123-design commented Mar 13, 2020

bigloudjeff commented Mar 13, 2020

dharmaturtle commented Mar 13, 2020 • edited

tahir-khalid commented Oct 9, 2020

vurso commented Oct 16, 2020

OmarElabd commented Oct 16, 2020

vurso commented Oct 16, 2020

igoyetche commented Nov 10, 2020

redwards510 commented Dec 2, 2020

vurso commented Dec 2, 2020 via email

ldy985 commented Dec 2, 2020

vreniose95 commented Apr 29, 2022

stefan-sherwood commented Jan 11, 2023

SteGriff commented Mar 5, 2020 •

edited

breadshort commented Mar 10, 2020 •

edited

dharmaturtle commented Mar 13, 2020 •

edited