-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Narrow down WindowsAzure.Storage usage #5479
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
Conversation
|
@azuresdkci Retest this please |
cormacpayne
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MiYanni some comments to take a look at
setup/azurecmdfiles.wxi
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MiYanni it looks like the wxi was regenerated before the CleanupBuild.ps1 script was run and removed all of the extra assemblies
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cormacpayne Are you referring to the last bullet in the guide? I didn't look at the changes to the Wxi file, because I wouldn't know what I'm looking for to be valid/invalid. I don't know Wxi files (not really something I'd assume most people are familiar with). It would probably make sense to require a clean repo prior to running the process instead of making a conditional check.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MiYanni it looks like there is still a reference to this package in the Commands.ApiManagement.ServiceManagement/packages.config file that should be removed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good find.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MiYanni should this be removed since it was removed in the .csproj file?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cormacpayne If the csproj doesn't need it, why would the package.config need it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MiYanni it looks like this wasn't removed in the corresponding packages.config file
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MiYanni it looks like this wasn't removed in the corresponding packages.config file
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MiYanni I don't think we need to add these references to Microsoft.Data.* and System.Spatial as they will get pulled in with WindowsAzure.Storage
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The assumption is incorrect. If it is not present in the packages.config, NuGet will not pull those packages. Dependent NuGet packages are not automatically pulled in. Instead, they simply state what other packages are required to be part of the packages.config file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MiYanni I don't think we need to add these references to Microsoft.Data.* and System.Spatial as they will get pulled in with WindowsAzure.Storage
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The assumption is incorrect. If it is not present in the packages.config, NuGet will not pull those packages. Dependent NuGet packages are not automatically pulled in. Instead, they simply state what other packages are required to be part of the packages.config file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MiYanni I don't think we need to add these references to Microsoft.Data.* and System.Spatial as they will get pulled in with WindowsAzure.Storage
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The assumption is incorrect. If it is not present in the packages.config, NuGet will not pull those packages. Dependent NuGet packages are not automatically pulled in. Instead, they simply state what other packages are required to be part of the packages.config file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MiYanni I don't think we need to add these references to Microsoft.Data.* and System.Spatial as they will get pulled in with WindowsAzure.Storage
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The assumption is incorrect. If it is not present in the packages.config, NuGet will not pull those packages. Dependent NuGet packages are not automatically pulled in. Instead, they simply state what other packages are required to be part of the packages.config file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MiYanni can we remove this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The .csproj doesn't reference Moq directly. So, it should be fine to remove it from the packages.config.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed.
|
@MiYanni Looks like some merge conflicts have come up - can you resolve? |
76b42eb to
5d2155b
Compare
|
@cormacpayne Finally got the solutions/projects working again after additional changes based on your comments (and other findings). Squashed commits. Please re-review. |
|
@MiYanni Can you fix the merge conflicts? |
|
@azuresdkci Retest this please |
|
@MiYanni Looks like a merge issue. Can you take a look? |
# Conflicts: # setup/azurecmdfiles.wxi
# Conflicts: # src/ResourceManager/Compute/Commands.Compute/packages.config
# Conflicts: # src/ResourceManager/Storage/Commands.Management.Storage/packages.config
|
@azuresdkci Retest this please |
2 similar comments
|
@azuresdkci Retest this please |
|
@azuresdkci Retest this please |
|
more on demands here: https://azuresdkci.westus2.cloudapp.azure.com/view/PowerShell/job/powershell-demand/571/ (and 572) |
Description
This is for #3430. It is an initial sweep of the projects to clean up dependencies. It removed several unused references to WindowsAzure.Storage and also allowed RedisCache to no longer require WindowsAzure.Storage (by updating a reference). The RedisCache team should review their project's changes to make sure they are good.
I did a fairly thorough check for each project to make sure that the .csproj references, the package.config, and the .psd1 aligned properly, and made sense keeping Common.Dependencies.targets in mind for the references. But, I definitely could have missed something, so a thorough review is required.
This checklist is used to make sure that common guidelines for a pull request are followed. You can find a more complete discussion of PowerShell cmdlet best practices here.
General Guidelines
Testing Guidelines
Cmdlet Signature Guidelines
ShouldProcessand haveSupportShouldProcess=truespecified in the cmdlet attribute. You can find more information onShouldProcesshere.OutputTypeattribute if any output is produced - if the cmdlet produces no output, it should implement aPassThruparameter.Cmdlet Parameter Guidelines