Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Workaround to use Azure SDK with RC2. (at least Storage) #1469

Closed
Bartmax opened this issue May 19, 2016 · 4 comments
Closed

Workaround to use Azure SDK with RC2. (at least Storage) #1469

Bartmax opened this issue May 19, 2016 · 4 comments

Comments

@Bartmax
Copy link
Contributor

Bartmax commented May 19, 2016

For people interested on using Azure SDK while there isn't a compatible version, I found a workaround. Is about using imports and bring a new version of the XmlSerializer as follows:

"dependencies":{
    "WindowsAzure.Storage": "7.0.1-preview",
    "System.Xml.XmlSerializer": "4.0.11-rc2-24027"
},
 "netcoreapp1.0": {
      "imports": [
        "dotnet5.6",
        "dnxcore50",
        "portable-net45+win8"
      ],

this works as standalone and portable in my minor testing. I can upload and access files. That's it. Didn't try anything else, so no guarantees. works on my machine ™

@davidfowl
Copy link
Member

/cc @pemari-msft

@ghost
Copy link

ghost commented May 21, 2016

Nice, do you know if we can do the same for all non compatible libraries aswell?

@davidfowl
Copy link
Member

All? No, it depends on what frameworks a package supports?

@aspnet-hello
Copy link

This issue is being closed because it has not been updated in 3 months.

We apologize if this causes any inconvenience. We ask that if you are still encountering this issue, please log a new issue with updated information and we will investigate.

natemcmaster added a commit that referenced this issue Oct 17, 2018
As a part of converging repos, we no longer need this code. It is currently buggy and slow, and we can get away without by hard-coding the repo graph (which rarely changes)
@ghost ghost locked as resolved and limited conversation to collaborators Dec 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants