Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
GitHub or Developer Community with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Created attachment 4251 [details]
MSBuild since 4.0 supports embedded property functions in attributes, which is documented as: http://msdn.microsoft.com/en-us/library/dd633440.aspx
We don't have support for that feature yet.
- extract the attachment
- go to TestClrFunctionExpression/TestClrFunctionExpression. There is a class library project.
- run: xbuild /t:TestEmbeddedFuncCall
The target is described in TestClrFunctionExpression.csproj.
Property functions are implemented in Mono 3.6.
What commit was that brought in at? I've got a parallell Mono, Version 220.127.116.11 installed and I still get an error "Unable to parse condition "$([System.String]::new('%(ReferencePath.Filename)').StartsWith('AutoMapper.')) : Invalid punctuation: [" in a build.
You want 63b6497 or later.
I made some further changes and this works with 357e5fe0ee9c2ef9462ce4669fc092d1aecf3d3c for me
Do the fixes for this also fix bug 3010 by any chance?
Andres, No it does not but for an example patch that fixes the parsing issues with that syntax see: bug 20634
It's not a complete fix since the Condition syntax doesn't evaluate the full expression correctly in all cases but that patch will fix the parsing errors at least.