ReSharper 9.1 extension not available from Extension Manager

[Joar Øyen]

Hi,

I updated my live template macros with the latest ReSharper SDK NuGet pacakge and made it depend on Wave 2.0. I'm able to add it to ReSharper 9.1 from a local feed (my development output folder), but I don't see it while searching the public repository from ReSharper -> Extension Manager. I can see my extension in the feed though: https://resharper-plugins.jetbrains.com/api/v2/curated-feeds/Wave_v2.0/Packages(Id='JoarOyen.ReSharper.LiveTemplates',Version='2.0.0.0')

After comparing my feed entry with your xUnit entry in the feed, I have false in the following two elements

<d:IsLatestVersion m:type="Edm.Boolean">false</d:IsLatestVersion>

<d:IsAbsoluteLatestVersion m:type="Edm.Boolean">false</d:IsAbsoluteLatestVersion>

Can this be the issue?

The source for my extension is available from this branch on GitHub: https://github.com/joaroyen/ReSharper.LiveTemplates/tree/Wave02

Thanks,

- Joar

[Matt Ellis]

Hmm. Those flags are a symptom, rather than the actual reason. The fact that they're false is why the extension isn't showing up in the extension manager, but they shouldn't be false. I've forced it by unlisting and then relisting the package. The properties are now true, and it should be in the extension manager now.

How did you upload the package? Via the command line, or the web interface?

Regards

Matt

[Slava Trenogin]

As far as I remember curators are not applied to packages uploaded through api. Yet another issue in the gallery.

--
You received this message because you are subscribed to the Google Groups "resharper-plugins" group.
To unsubscribe from this group and stop receiving emails from it, send an email to resharper-plug...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Matt Ellis]

I think we're ok with that - it was added to the feed, but it hadn't updated the latest flags correctly. I'll run through the tests again.

On Monday, 13 April 2015 21:15:46 UTC+1, slava.trenogin wrote:

As far as I remember curators are not applied to packages uploaded through api. Yet another issue in the gallery.

On Monday, April 13, 2015, Matt Ellis wrote:

Hmm. Those flags are a symptom, rather than the actual reason. The fact that they're false is why the extension isn't showing up in the extension manager, but they shouldn't be false. I've forced it by unlisting and then relisting the package. The properties are now true, and it should be in the extension manager now.

How did you upload the package? Via the command line, or the web interface?

Regards

Matt

On Monday, 13 April 2015 18:43:51 UTC+1, Joar Øyen wrote:

Hi,

I updated my live template macros with the latest ReSharper SDK NuGet pacakge and made it depend on Wave 2.0. I'm able to add it to ReSharper 9.1 from a local feed (my development output folder), but I don't see it while searching the public repository from ReSharper -> Extension Manager. I can see my extension in the feed though: https://resharper-plugins.jetbrains.com/api/v2/curated-feeds/Wave_v2.0/Packages(Id='JoarOyen.ReSharper.LiveTemplates',Version='2.0.0.0')

After comparing my feed entry with your xUnit entry in the feed, I have false in the following two elements

<d:IsLatestVersion m:type="Edm.Boolean">false</d:IsLatestVersion>

<d:IsAbsoluteLatestVersion m:type="Edm.Boolean">false</d:IsAbsoluteLatestVersion>

Can this be the issue?

The source for my extension is available from this branch on GitHub: https://github.com/joaroyen/ReSharper.LiveTemplates/tree/Wave02

Thanks,

- Joar

--
You received this message because you are subscribed to the Google Groups "resharper-plugins" group.

To unsubscribe from this group and stop receiving emails from it, send an email to resharper-plugins+unsubscribe@googlegroups.com.

[Joar Øyen]

I used command line to push the updated package.

The relisting did the trick and I was able to install it now.

Thanks,

- Joar

[Julien Lebosquain]

Matt, Slava: for information, the exact same thing happened to me with Enhanced Tooltip right now (uploaded via command line).
Unlisting/Relisting did the trick.

[Matt Ellis]

Thanks Julien. I'll definitely look into this.