3

I don't see Microsoft.ServiceFabric.Services.Remoting version 3.3.624 anymore:

Microsoft.ServiceFabric.Services.Remoting version 3.3.622

Microsoft.ServiceFabric.Services.Remoting version 3.3.622

My existing projects refer to 3.3.624:

Microsoft.ServiceFabric.Services.Remoting version 3.3.624

Microsoft.ServiceFabric.Serices.Remoting version 3.3.624

I get an NU1605 error Detected package downgrade.

Should I follow this approach for this NU1605 Detected package downgrade error?

I am more curious as to why 3.3.624 just vanished!!!

Is downgrading existing references from 3.3.624 to 3.3.622 the only way to solve this prolbem? Or am I doing something wrong in referencing the versions?

Super Jade
  • 5,609
  • 7
  • 39
  • 61
Harshith Reddy
  • 124
  • 2
  • 11
  • I opened [GitHub issue 24021](https://github.com/MicrosoftDocs/azure-docs/issues/24021) to ask why Microsoft.ServiceFabric.Services.Remoting version 3.3.624 is no longer available. Strangely, I seem to have version 3.3.624 available on one machine, but on my other machine I can install only 3.3.622. – Super Jade Feb 01 '19 at 22:15

1 Answers1

4

To answer your questions

I am more curious as to why 3.3.624 just vanished!!!

and

Is downgrading existing references from 3.3.624 to 3.3.622 the only way to solve this prolbem?


From MicahMcKittrick's response to the GitHub issue I created:

The owner has unlisted this package. This could mean that the package is deprecated or shouldn't be used anymore.

So you'll have to downgrade Microsoft.ServiceFabric.Services.Remoting to 3.3.622, the current latest version or upgrade to a newer version.

Super Jade
  • 5,609
  • 7
  • 39
  • 61
  • 1
    SF team recently [released](https://blogs.msdn.microsoft.com/azureservicefabric/2019/02/04/azure-service-fabric-6-4-refresh-release/) the version `x.x.624` and `x.x.622`of SF Runtime, Seems that the `.624` does not need new packages, the release details mentions only bugs fixes on windows, the new SDK should be `3.3.622.9590`. Looking on nuget, they just released a new version of packages `3.3.638`, might fix the issue with different versioning. – Diego Mendes Feb 05 '19 at 09:22