Skip to content

Fix issue importing an SDK via Import element.#2038

Merged
AndyGerlicher merged 3 commits intodotnet:vs15.3-previewfrom
AndyGerlicher:importsdkfix
May 1, 2017
Merged

Fix issue importing an SDK via Import element.#2038
AndyGerlicher merged 3 commits intodotnet:vs15.3-previewfrom
AndyGerlicher:importsdkfix

Conversation

@AndyGerlicher
Copy link
Contributor

  • This feature was regressed in Add support for SDK Resolvers #2002
  • Update unit tests to verify functionality
  • Update ProjectParser to parse SDK name/version values and construct an SdkReference object to be used by the evaluator.

Closes #2034

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So explicit attributes instead of fancy string that needs to be parsed?

The XSD should probably be updated at some point, since SDKs introduced a couple of new attributes / elements.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 on xsd update

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add a new test to construction editing tests to assert null values, non-null values, etc. For example, what happens if you add an SDK import element inside an import group group together with non SDK import elements.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why the spaces?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 on xsd update

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure I understand the motivation for this. Can you elaborate?

@AndyGerlicher AndyGerlicher changed the base branch from master to vs15.3-preview May 1, 2017 22:01
* This feature was regressed in dotnet#2002 * Update unit tests to verify functionality * Update ProjectParser to parse SDK name/version values and construct an SdkReference object to be used by the evaluator. Closes dotnet#2034
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

5 participants