Is there a way I can download the March version of GenPro 3.5? Yesterday I updated to the June 27th 2012 version. After that I did a refresh of the database schema in GenPro and received an exception. LLBLGen is crashing and not letting me continure. The exception posted below indicates a name that had not changed anywhere, so I would like to re install the older version to see if it is an issue with the New Build or something in the schema that is causing the issue. I want to test this against the two builds to determine if there is a difference before I submit a bug report.

Thanks

Here is stack trace.

Exception information.

LLBLGen Pro version: v3.5. Build: June 27th, 2012

Exception details:

Message: The name is not CLS compliant and/or is not usable as an identifier and/or isn't compliant with the name construction properties of the project: Original name value:'Protocol_CompanyCmpName', CLS compliant version: 'ProtocolCompanyCmpName' Source: SD.LLBLGen.Pro.Core Stack trace: at SD.LLBLGen.Pro.Core.CoreUtils.ValidateDefault[TValue](TValue valueToValidate, Boolean checkForDuplicates, Boolean throwOnError, IValidator1 validator, String propertyName, ErrorContainer loggedErrors, Boolean isSoftError, TValue& correctValue) at SD.LLBLGen.Pro.Core.CoreUtils.ValidateString(String stringToValidate, Boolean checkForDuplicates, Boolean throwOnError, String originalValue, IValidator1 validator, String propertyName, ErrorContainer loggedErrors, Boolean isSoftError, String& correctValue) at SD.LLBLGen.Pro.Core.CoreUtils.Validate[TValue](TValue valueToValidate, TValue originalValue, IValidator1 validator, Boolean checkForDuplicates, Boolean throwOnError, String propertyName, ErrorContainer loggedErrors, Boolean isSoftError, TValue& correctValue) at SD.LLBLGen.Pro.Core.GeneralDataStructures.ValidatableMember2.ValidateMemberValue(TValue valueToValidate, Boolean checkForDuplicates, Boolean throwOnError, TValue& correctValue) at SD.Tools.Algorithmia.GeneralDataStructures.CommandifiedMember2.set_MemberValue(TValue value) in C:\Myprojects\VS.NET Projects\Algorithmia_hg\SD.Tools.Algorithmia\GeneralDataStructures\CommandifiedMember.cs:line 373 at SD.LLBLGen.Pro.ApplicationCore.EntityModel.FieldElement.SD.LLBLGen.Pro.ApplicationCore.IFieldElementCore.set_Name(String value) at SD.LLBLGen.Pro.ApplicationCore.EntityModel.EntityDefinition.PerformFixDuplicateNamesAfterRefresh(LogNode parentLogNode) at SD.LLBLGen.Pro.ApplicationCore.ProjectClasses.Project.FixDuplicateNamesAfterRefresh(LogNode parentLogNode) at SD.LLBLGen.Pro.ApplicationCore.ProjectClasses.Project.RefreshMetaData(String driverID, List1 populatedCatalogs, UserConfiguration preferences) at SD.LLBLGen.Pro.Gui.Classes.GuiController.PerformRefreshMetaDataAction(String driverID) at SD.LLBLGen.Pro.Gui.Controls.CatalogExplorer._commandManager_CommandClick(Object sender, CommandEventArgs e) at Janus.Windows.UI.CommandBars.UICommandCollection.c(Object , CommandEventArgs ) at Janus.Windows.UI.CommandBars.UICommand.ar() at Janus.Windows.UI.Internal.JNSCZ.OnMouseUp(MouseEventArgs e) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at Janus.Windows.UI.Internal.JNSCZ.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Inner exception: <null>

It's likely a bug in the refresher, although not one we are aware of. Could you give us a repro case with your current project and the database schema you have in your database? So your current llblgenproj file and the current db schema is enough.

Please open a helpdesk thread to attach the files, so only we can access them. Please refer to this thread in your helpdesk thread so we can have a look.

Also, if you create a new project from the database (just for testing), does that succeed, or do you get the same exception?

We actually had a bugfix in may which transformed an exception related to validation into a proper error message in the log.