Package downgrade for WindowsAzure.Storage 7.0.1-preview #16662
Comments
|
Azure storage should update to latest packages that support generations rather than hand-selecting old pre-release versions. They may be waiting for a public release of those packages on nuget, but if not they can do this today. Just point the project and dotnet-core myget feed and update all. |
|
Short of pulling their source into my projects, there is nothing that can be done on our sides AFAICT, so I'll hope for a new preview package from their team. As you can see, I tried to discuss this with them, and they didn't feel it was a priority. Actually, they wouldn't discuss it at all 😢. @davidfowl told me what they are doing is "a problem" and to open this issue on it. However, should I close unless/until something actually breaks? |
|
Downgrades are always breaking. It means things can be running under torn state. This could result in ref-def mismatch on load or worse, random different behavior. I do think that the uber problem here is that they need to update dependencies to a consistent newer LKG. They may just be waiting for us to put that LKG on nuget. If you reference a higher version won't it suppress nuget's warning? |
|
@ericstj I'll definitely try that asap. I have an interview tomorrow with a company who thinks this homepage passes for good web dev ... You probably feel about the same way I do on that ... let me talk some sense to them (and about adopting .NET Core!!!) and I'll try your suggestion on the package downgrade and get back to you. |
|
@ericstj Tried ... ... resulted in ... ... so I tried ... Licked it ... warnings gone and the library seems to function normally. I'll leave to you to close when appropriate. With the next Azure Storage preview/release, I'll check and ping back or re-open if the downgrade repros. |
|
@ericstj Update: The Azure Storage team just released "System.Xml.XmlSerializer": "4.0.11-*",
"System.Runtime.Serialization.Primitives": "4.0.11-beta-23409"My apps work, so I'm ok right now. This is just an update here. |
|
@ericstj... and one new package downgrade has cropped up with the new Azure Storage library ...
... so I went looking for ... and the "dependencies": {
"System.Console": "4.0.0-*",
"WindowsAzure.Storage": "7.0.1-preview",
"System.Xml.XmlSerializer": "4.0.11-*",
"System.Runtime.Serialization.Primitives": "4.0.11-beta-23409"
},
"description": "GuardRex Corporation AppExceptions NuGet package.",
"frameworks": {
"netstandard1.5": {
"imports": [ "dnxcore50", "portable-net451+win8" ]
}
},
"runtimes": {
"win81-x64": {}
},I don't think this is breaking me right now, so this is just an FYI. |
|
This is just a symptom of `Microsoft.WindowsAzure.Storage needing to rebuild against the latest CoreFx packages. We make this work correctly at runtime because we're still shipping the incremented versions in the implementation assembly, but for compatibility with desktop we had to move the reference assembly back to 4.0.10.0. |
guardrex
changed the title
|
@ericstj ... and the hits just keep on com'in with To deal with ... an ... so went to ... ... to silence everything, I still can't get a restore ... David says 'you have packages that bring in old versions of stuff.' Well, "they" would sound a little better, but I take the point. Next, I'm going to try to clone them and fix their packages, and I have very little confidence that I'll be able to do that. We'll see. |
|
Imports isn't a good solution, that means you'll end up picking up a PCL group from the packages that doesn't list dependencies. Instead just reference without imports and deal with the old references by referencing the latest from your project. |
|
@ericstj Thanks, but I decided to punt on this. I'm in the process of implementing Azure Storage REST API. Since there is nothing wrong other than that team not keeping their preview (or a preview) up with latest over here, I'm going to close this. I'll go back to their lib when they catch up, perhaps RTM-time. Thanks again for your help. |
|
Note for temporary reference as we wait on an updated Azure Storage lib for RC2 release: I just found out from @Bartmax that ... will get the whole package restored. However, |
|
I suspect the Azure Storage SDK team are waiting for .NET Core packages from their upstream dependencies before starting their own work.
Then there's OData, which doesn't seem to be aware that the .NET world is changing around them, so I've opened an issue there. This all needs to be much more joined up. Getting libraries and packages across the Microsoft ecosystem up and running on Core should be Priority 1 for SDK teams for the next six weeks. |
|
@markrendle They're working on it now. Azure/azure-storage-net#274 |
|
workaround: dotnet/aspnetcore#1469 |
ghost
locked as resolved and limited conversation to collaborators
RE:
WindowsAzure.Storage 6.2.2-previewThere is a package downgrade occurring (
System.Xml.XmlSerializer) fordotnet cliprojects on the CI feed going on over a month now ...The Storage folks don't think they can do anything about this ...
Azure/azure-storage-net#230
... but they pinned to an old package ...
https://github.com/Azure/azure-storage-net/blob/master/Lib/AspNet/Microsoft.WindowsAzure.Storage/project.json#L52
@davidfowl suggested that I open this here and cc: @ericstj.
For reference: https://www.nuget.org/packages/System.Xml.XmlSerializer/
.NET Command Line Tools (1.0.0-beta-001653)
Product Information:
Version: 1.0.0-beta-001653
Commit Sha: 1fccdbd6ec
Runtime Environment:
OS Name: Windows
OS Version: 10.0.10240
OS Platform: Windows
Runtime Id: win10-x64
The text was updated successfully, but these errors were encountered: