Completed
Last Updated: 22 Oct 2015 08:30 by ADMIN
ADMIN
Cody
Created on: 10 Sep 2015 17:17
Type: Bug Report
0
Element with special symbol causes compile error
If you have two elements whose name only differ by a special symbol (see attached screen shot) it will result in a compile error like this:

f:\Dropbox\Support Issues\Client Site - Copy\Pages.g.cs: Line 89: (CS0102) The type 'Client_Site.Pages.IFLFXecutePaymentsSystem20Page.ExpressionDefinitions' already contains a definition for 'TableCell'
f:\Dropbox\Support Issues\Client Site - Copy\Pages.g.cs: Line 79: (CS0102) The type 'Client_Site.Pages.IFLFXecutePaymentsSystem20Page' already contains a definition for 'TableCell'

Sample project demonstrating the problem is attached.

The correct fix may be to NOT record element names with special symbols.
1 comment
ADMIN
Daniel Djambov
Posted on: 19 Oct 2015 13:13
Telerik: the actual problem here is different - how we got to a state to record an element with a special symbol in its name - this should not be allowed. We have logic in our recording mechanism, as well in our rename element validation to not allow such behavior. The error that states 2 elements with same name exist is a side effect and is expected as we skip special symbol upon compilation.
We are unable to reproduce this with our latest product release R3 2015 and cannot implement a fix for this build problem, we should rather investigate how such element was recorded on the first place, but we are unable to get it with client site. If you can confirm you can still get such elements recorded with latest product release, we can process this item further. Thank you for the feedback.