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.

Sign up for GitHub

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

Jump to bottom

Migrate to use portable profile 111 and also regenerate library code using the latest client runtime #1269

Merged
merged 1 commit into from
Jul 21, 2015
Merged

Migrate to use portable profile 111 and also regenerate library code using the latest client runtime #1269

merged 1 commit into from
Jul 21, 2015

Conversation

yugangw-msft
Copy link
Contributor

Note: This PR should fail till the test framework package gets migrated to use the same adal library like runtime does.
This PR will also fix #1264

@yugangw-msft yugangw-msft changed the title migrate to using profile 111 and regenerate library code using the latest client runtime Migrate to use portable profile 111 and also regenerate library code using the latest client runtime Jul 21, 2015
@tonytang-microsoft-com
Copy link
Contributor

@yugangw-msft I think below references will be included by the common props, and rp proj doesn't have to include them. Right?

    <Reference Include="System" />
    <Reference Include="System.Net.Http" />
    <Reference Include="System.Runtime.Serialization" />

stankovski added a commit that referenced this pull request Jul 21, 2015
@stankovski
Merge pull request #1269 from yugangw-msft/111
9c8ba4d 
Migrate to use portable profile 111 and also regenerate library code using the latest client runtime
@stankovski stankovski merged commit 9c8ba4d into Azure:AutoRest Jul 21, 2015
@yugangw-msft yugangw-msft deleted the 111 branch November 9, 2015 21:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@yugangw-msft @tonytang-microsoft-com @stankovski @azurecla