-
Notifications
You must be signed in to change notification settings - Fork 26
Unable to install in VS 2019 #61
Comments
As a temporary work around while the search for someone to merge the referenced PR continues, you can download the vsix, open it with 7-zip (or change ext to .zip), modify the the extension.vsixmanifest file just like the referenced PR does and it will install. Not sure if any negative consequences but at least it works! |
Hello. I see that the PR was merged, but this is still not working when I attempt to install it from the marketplace. Edit: I see that it was last updated on 2018 in the marketplace. |
Still nothing? This was a really awesome extension :( |
@AdamDotNet your workaround worked easily. Thanks for sharing! |
Are there any updates or alternatives for this extension? |
@madskristensen Do you know anything? |
No, sorry |
Can somebody please update the Visual Studio Marketplace (which still has not been updated since 2018-10-17) to the latest version that includes the workaround discussed in this issue? |
@madskristensen said in PR #62 (comment):
Is that still the plan? Looks like @KirillOsenkov was able to merge the PR |
@bricelam I can upload to marketplace, but not build it. Once I have a signed .vsix I can push it to the Marketplace. Alternatively, fork this repo, change the Product ID and upload it under a new name and account |
project.json, MyGet, and TeamCity, oh my! This repo needs some love. Do we know which team owns it? |
@bricelam I think it's the .NET team since it extends the .csproj file editor features. |
lol, that doesn't narrow it down much. (Technically, Smit and I are part of the .NET team, but we work on Entity Framework.) @glennc Any ideas? Looks like most of the contributors have ties to Roslyn... |
I think it could have been @davkean's former team |
Are there any updates or alternatives for this extension? |
Installed product versions
Description
Installer does not work
Current behavior
Explain what it's doing and why it's wrong

Expected behavior
Install the extension
The text was updated successfully, but these errors were encountered: