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 7084 [details]
Hacky fix to the tokenizer and parser.
At least part of the problem is in the ConditionTokenizer and ConditionParser classes.
I've attached a patch that rather hackily adds the tokenizer and parser support. I suspect a proper fix would probably entail merging the Expression and ConditionExpression parsing though.
There is still an issue with the evaluation of the expressions in one of my builds that I haven't had a chance to figure out yet. That build is too big to upload here. If I can get a reproducible example that is small I'll upload it.
What condition syntax are you trying to fix?
An example syntax that fails:
The embedded property syntax recently added works elsewhere just fine. But the Condition expressions have their own tokenization and parsing on top of the regular expression parsing.
This is a part of the Automapper nuget packages .targets file.
Fixed in master