IMPORTANT NOTE: BECAUSE OF CHANGES IN THE DataSource IDs it could happen that some browse or form properties get confused and map to a different entity. This ONLY could happen in tables which have Self-Relations like for Example Northwind.Employees which has a relation to itself.
New Features
 | Better non sortable types exclusion. |
In several template options we allowed the user to select a property. In some scenarios this property
was used for example to sort a dropdown, etc. Before we showed just ALL properties from the BO and this could give runtime errors when trying to run
the asp.net application.
Typically the error message would read something like:
"The text, ntext, and image data types cannot be used in an ORDER BY clause.
Source Editor
| 2 bugs fixed which caused Error Report windows to appear under certain specific cases. |
NHibernate Templates
| We added some more User Codeblocks to the XML mapping file. This was needed for example for manually added <version> or <timestamp> tags |
| We now use full naming when referring to the NHibernate.Expression.Order to avoid obvious name conflict in case you had a Table called Order in your Database Repository. |
| By default the generation directory is dynamically configured using Mydocuments,etc. If the result of that calculation is not valid there was a warning message that should explain that fact so the developer can manually configure a correct default generation directory. Instead of getting that explanation msg this exception ocurred: Message (genwise):Index (zero based) must be greater than or equal to zero and less than the size of the argument list. Title (genwise):Unhandled Exception Exception Type:System.FormatException |
Database Repository
Import Schema
| SQL SERVER : On certain case-sensitive versions of MsSQL it could happen that Import Schema would fail when importing Relations. Error: Invalid column name 'Constraint_catalog'. |
| If the table had a name using "only" vowels AND it was shorter than 3 chars --> exception ( Exception List1) Index and length must refer to a location within the string. Parameter name: length at System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean fAlwaysCopy) at ) |
Compare Schema
| ERS#2638: Fixed a thread bug that could give errors if the compare button was clicked several times ( several threads where launched giving connection errors) Now this has been replaced with a nice msg explaining the situation.. |
| ERS#2639: When importing a Relation it "could" happen that the FK Column is not present in the DB Repository Table. This would be quite common if the table is a new added table + fk.The compare was failing with an exception when the Column was not found. |
GenWise IDE
Template Option (symbol) Editor
| ERS#2640 : The Entity details tab gives an exception when used for the 2nd time. It has to do with the fact that the tab is disposed.. |
| Optimization : change event was fired even when the value did not changed causing extra unnecessary re-generations. |
| ERS#2649 : Exception about Primary Control not implemente when selecting Templates of Type "BoundPropertyTemplate". This occurred because default implementation of Primary control was raising an exception instead of returning null. Null should be a possible value for the PrimaryControl property. |
| ERS#2565 : Incorrect question for saving Relation.Are you sure you want to close this window - the relation has not been saved This popup appears after creating a relation, clicking Save Changes in the relation editor window, and then closing it. It also appears when opening a relation window, not making any changes and then closing it again. |
| Removed and experimental tab called "Item Calls" |
ASP.NET Templates
| ERS#2650 : Changing the caption of a Form Template was not been moved into the detailsview caption property. |
| ERS#2651 : Each property template has Visibility options. These options allows the user to, in a very simple way, avoid showing a certain property in the form based on the Action. the code needed for dynamically hide it was not generated (fixed) |
| ERS#2652 : |
| ERS#2656 : If a relation was deleted with asp.net project closed and then the project was opened again --> an exception was raised.Now it actually shows the template invalid and allows the user to remove the template. |
| ERS#2658 (regression) : The FormTemplate when used with FormView control was not showing the IsLookup properties templates. |
| New User Codeblock : Form object primming. |
WFD (Web Form Designer)
| ERS#2646 : Important bug when the Templates "switch" a control. The switching/replacing of controls does not ocurr very ofter but it happens when for example you decide to change the Form Template to use FormView instead of DetailView. The replacement of controls worked correctly but if the "old" |
control had "related HTML" that html was lost.
| ERS#2643 : Fixed issue with WFD raising exception when trying to "edit" an image url. |
| ERS#2660 (Serious): If a Page contained HTML User CodeBlocks AND the designer was used for the 1st time AFTER loading AND there has been no previous REGENERATION of the item -->those user CodeBlocks (html) where lost. |
| ERS#2661: Using <BR> inside a Template-based control like DetailsView, gridview, etc was making the parsing service fail. Not only that, actually, it was catched and shown as an error msg instead of we getting an exception report. |
| When using FormView the design could get corrupted if designer was used after opening of the project. |
| When a WFD is closed there is a feature to automatically give focus to the Project Explorer. But the project explorer could be closed and if that was the case --> exception. |
Template Framework
| Class Builder: When more than 1 attribute is present a separator (,) was not generated causing compile errors. (this was not needed until v1.02 that we are now generating multiple attributes). |