Infragistics 2016.1

1. EditorFor Bug - Edit Complex Object

Using Infragistics IgniteUI controls by MVC helper in MVC EditorTemplates and Html.EditorFor() for object propertys (complex objects) isn't working at all.
Controls are not rendered, because generated id of DOM element element do not match to id generated in Javascript code (wrong jQuery selector).
If control Javascript init code is rendered, unusual id and/or invalid input name is generated. With invalid input name a mapping to the object property by MVC default value provider on POST will not function.

Example:

<div id="Residence_IsNice"></div>
<script type="text/javascript">$(function () {$('#Residence.IsNice').igCheckboxEditor({ checked: false, validatorOptions: { required: { errorMessage: 'Das Feld "IsNice" ist erforderlich.' }, messageTarget: 'IsNice' }, inputName: 'Residence.IsNice' });});</script>

2. Initial Value Bug

Initial value in rendered Javascript code has wrong format for some controls generated with MVC helper (DateEditorFor, DatePickerFor, NumericEditorFor, PercentEditorFor), initial value can not be parsed or parsed value is wrong. Reason: Initial value string is generated culture dependent (perhaps .toString() was used). A string that can be parsed or an appropriate value should be generated.

Example:

<div id="theDateEditor"></div>
<script type="text/javascript">$(function () {$('#theDateEditor').igDateEditor({ value: '20.05.2016 12:34:52', validatorOptions: { required: { errorMessage: 'Das Feld "PropDateTime" ist erforderlich.' }, messageTarget: 'PropDateTime' }, inputName: 'PropDateTime' });});</script>

Microsoft MVC project demonstrating these bugs attached (nuget packages and Infragistics files removed).