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

Fix NuGet downgrade warnings in the build #2396

Closed
davidfowl opened this Issue Mar 25, 2016 · 4 comments

Comments

Projects
None yet
6 participants
@davidfowl
Member

davidfowl commented Mar 25, 2016

They are several of them

/cc @emgarten

@emgarten emgarten added this to the 3.5 Beta milestone Mar 28, 2016

@emgarten emgarten self-assigned this Mar 28, 2016

@yishaigalatzer yishaigalatzer modified the milestones: 3.5 Beta, 3.5 RC Mar 31, 2016

@rrelyea rrelyea assigned TimBarham and unassigned emgarten May 5, 2016

@rrelyea

This comment has been minimized.

Show comment
Hide comment
@rrelyea

rrelyea May 5, 2016

Contributor

Can you please catalog the current warnings, and loop us in.

Contributor

rrelyea commented May 5, 2016

Can you please catalog the current warnings, and loop us in.

@TimBarham

This comment has been minimized.

Show comment
Hide comment
@TimBarham

TimBarham May 10, 2016

Member

Downgrade warnings are all gone. Will look at some of the build warnings just to clean things up.

Member

TimBarham commented May 10, 2016

Downgrade warnings are all gone. Will look at some of the build warnings just to clean things up.

@rrelyea rrelyea added the Type:Bug label Jun 9, 2016

@TimBarham

This comment has been minimized.

Show comment
Hide comment
@TimBarham

TimBarham Jul 5, 2016

Member

@drewgil looked at the remaining build warnings (which are about VS related assembly version conflics) - I believe he came to the conclusion that they are not able to be resolved.

Member

TimBarham commented Jul 5, 2016

@drewgil looked at the remaining build warnings (which are about VS related assembly version conflics) - I believe he came to the conclusion that they are not able to be resolved.

@TimBarham TimBarham closed this Jul 5, 2016

@TimBarham TimBarham modified the milestones: 3.5 Beta2, 3.6 Beta Jul 5, 2016

@drewgillies

This comment has been minimized.

Show comment
Hide comment
@drewgillies

drewgillies Jul 5, 2016

Contributor

@rrelyea @TimBarham: Correct. Most of the remaining warnings are caused by version conflicts on the dependencies Microsoft.Build and Microsoft.Build.Framework--version 4.x.x.x are dependencies of the .NET Framework 4.6, and 14/15.x.x.x are dependencies of project system assemblies. It's an MSB warning and as such cannot be suppressed; app.config changes don't remove the warning from command line builds. VS version-redirects these dependencies to 14/15.x.x.x so there is no runtime conflict.

Other than these, we have some EnvDTE embed interop types inconsistencies which generate warnings (relatively few).

Contributor

drewgillies commented Jul 5, 2016

@rrelyea @TimBarham: Correct. Most of the remaining warnings are caused by version conflicts on the dependencies Microsoft.Build and Microsoft.Build.Framework--version 4.x.x.x are dependencies of the .NET Framework 4.6, and 14/15.x.x.x are dependencies of project system assemblies. It's an MSB warning and as such cannot be suppressed; app.config changes don't remove the warning from command line builds. VS version-redirects these dependencies to 14/15.x.x.x so there is no runtime conflict.

Other than these, we have some EnvDTE embed interop types inconsistencies which generate warnings (relatively few).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment