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

Convert Azure hosting startup and integration projects to use ProjectRef #6207

Merged
merged 2 commits into from
Jan 2, 2019

Conversation

natemcmaster
Copy link
Contributor

Implements #4246 for a subset of projects in src/AzureIntegration.

There is still code left in src/AzureIntegration. It's unclear if this code needs to be kept. I've started email to figure out if it's okay to delete the left over code in src/AzureIntegration which was used for these projects:

  • Microsoft.Extensions.ApplicationModelDetection (a package that never shipped)
  • Runtime SiteExtension - never shipped after 2.1.0 and 2.2.0 RTM. May not be needed in servicing
  • The SDK site extension which includes the SDK - never shipped after 2.1.0 and 2.2.0 RTM, and will not ship in 3.0.

rynowak added a commit to dotnet/razor that referenced this pull request Dec 31, 2018
The bug here is that we have extra whitespace being written out when the
component renders. This happens because parser adds an empty C#
statement node to wrap all of the whitespace that precedes `@functions`.
This is tracked by dotnet/aspnetcore#6207.

To fix this issue I'm allowing the whitespace pass to skip over an empty
C# statement to remove whitespace. This is sound because an empty C#
statement produces no output - we allow removing whitespace before and
after all nodes that produce no output.
rynowak added a commit to dotnet/razor that referenced this pull request Dec 31, 2018
The bug here is that we have extra whitespace being written out when the
component renders. This happens because parser adds an empty C#
statement node to wrap all of the whitespace that precedes `@functions`.
This is tracked by dotnet/aspnetcore#6207.

To fix this issue I'm allowing the whitespace pass to skip over an empty
C# statement to remove whitespace. This is sound because an empty C#
statement produces no output - we allow removing whitespace before and
after all nodes that produce no output.
This code was written for a partner team, but never shipped to customers
@natemcmaster
Copy link
Contributor Author

Updated to remove Microsoft.Extensions.ApplicationModelDetection

@natemcmaster natemcmaster merged commit d66537c into dotnet:release/2.1 Jan 2, 2019
@natemcmaster natemcmaster deleted the azure-integration branch January 2, 2019 17:56
JunTaoLuo pushed a commit that referenced this pull request May 7, 2020
The bug here is that we have extra whitespace being written out when the
component renders. This happens because parser adds an empty C#
statement node to wrap all of the whitespace that precedes `@functions`.
This is tracked by #6207.

To fix this issue I'm allowing the whitespace pass to skip over an empty
C# statement to remove whitespace. This is sound because an empty C#
statement produces no output - we allow removing whitespace before and
after all nodes that produce no output.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants