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

Update attribute can only appear in static items #1620

Closed
wants to merge 1 commit into from

Conversation

cdmihai
Copy link
Contributor

@cdmihai cdmihai commented Jan 27, 2017

Resolves #1618

@nguerrera
Copy link
Contributor

Can we take this to ship room? I think we need this in RTW

@rainersigwald
Copy link
Member

@nguerrera I don't think it meets the bar now, but we can bring it up in standup today.

@nguerrera
Copy link
Contributor

Isn't it a now or never language change? Does bar sill have that. This feels like silent bad code gen equivalent for msbuild. It would be breaking to make it work as I expect if not an error now.

@nguerrera
Copy link
Contributor

nguerrera commented Jan 27, 2017

Also breaking to go from non error to error

@cdmihai
Copy link
Contributor Author

cdmihai commented Jan 27, 2017

Ideally, the correct thing to do is to error now for RTW, to increase the user friendliness and debug-ability. And then, post RTW, allow Update for targets too. Along with everything else in #1124.

Prior to dev15, msbuild did have an Update only for dynamic items (items in targets). It works like this: #955. This is the code path that hits if you put an Update inside targets. The Update gets ignored and the old behaviour kicks in, which is equivalent to <Compile Update="@(Compile)">.

More details here.

@nguerrera
Copy link
Contributor

Agree on error now support later.

I'm aware of the existing target mechanism, but it is cumbersome. Could you guys look at my use case in the bug comment and let me know how to express it with just a condition?

@rainersigwald
Copy link
Member

I was just surprised this didn't happen. Did we decide not to make this an error? Did we just miss shiproom? I don't remember at all :(

@cdmihai
Copy link
Contributor Author

cdmihai commented May 9, 2017

Same here, no idea what happened. My vague memory is ship-room miss-alignment. Should we bring the error back? Or just wait until we port Update to targets?

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.

4 participants