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

Provide option for msbuild properties #1549

Merged
merged 2 commits into from
Apr 14, 2017
Merged

Provide option for msbuild properties #1549

merged 2 commits into from
Apr 14, 2017

Conversation

vicancy
Copy link
Contributor

@vicancy vicancy commented Apr 14, 2017

for #1518 & #1254

@qinezh
Copy link
Contributor

qinezh commented Apr 14, 2017

:shipit:

@@ -38,7 +38,7 @@ public BuildInfo GetValidConfig(IEnumerable<string> inputProjects)
return GetConfig(key);
}

public void SaveToCache(IEnumerable<string> inputProjects, IDictionary<string, List<string>> containedFiles, DateTime triggeredTime, string outputFolder, IList<string> fileRelativePaths, bool shouldSkipMarkup)
public void SaveToCache(IEnumerable<string> inputProjects, IDictionary<string, List<string>> containedFiles, DateTime triggeredTime, string outputFolder, IList<string> fileRelativePaths, bool shouldSkipMarkup, IDictionary<string, string> msbuildProperties)
Copy link
Contributor

Choose a reason for hiding this comment

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

create a class for parameters?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

will do refactor later

@vwxyzh
Copy link
Contributor

vwxyzh commented Apr 14, 2017

:shipit:

@vicancy vicancy merged commit 4fc7083 into dotnet:dev Apr 14, 2017
@vicancy vicancy deleted the fix branch April 14, 2017 06:34
vicancy added a commit that referenced this pull request Apr 14, 2017
* Provide option for msbuild properties

* Update RELEASENOTE.md
@ericdrobinson
Copy link

Does this Issue perchance cover preprocessor symbol handling as suggested in #1518?

or at least specify C# preprocessor symbols to define?

We have some APIs that are only generated for certain builds where certain Preprocessor Symbols are defined. It would be awesome if the same symbols specified when building assemblies could similarly affect the generated documentation (i.e. make generated documentation content match the generated code content)...

@macrogreg
Copy link

The merge command described in the release notes for this PR is not actually working (#3067, #7106).

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.

6 participants