I'm getting the following error when running codegen

Name cannot begin with the '[' character, hexadecimal value 0x5B. Line 36, position 18.

LLBLGen Pro version 4.0. Build April 9th, 2013 -----[Core exception]-------------------- at System.Xml.XmlTextReaderImpl.Throw(String res, String[] args) at System.Xml.XmlTextReaderImpl.ParseQName(Boolean isQName, Int32 startOffset, Int32& colonPos) at System.Xml.XmlTextReaderImpl.ParseElement() at System.Xml.XmlTextReaderImpl.ParseElementContent() at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace) at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc) at System.Xml.XmlDocument.Load(XmlReader reader) at System.Xml.XmlDocument.LoadXml(String xml) at SD.LLBLGen.Pro.TaskPerformers.ProjectFileCreator.ConstructProjectFileContents(StringBuilder outputText, String projectName, String binRootFolder, String fullPath) at SD.LLBLGen.Pro.TaskPerformers.ProjectFileCreator.ProduceFileContents(String projectName, String templateID, String templateBindingDefinitionName, String fullPath, String destinationFilename, FileAction actionToTake, String binRootFolder, TargetVersion versionToTarget, String& actionTypeForLog) at SD.LLBLGen.Pro.TaskPerformers.ProjectFileCreator.Perform(IGenerator executingGenerator, ITask taskDefinition, Dictionary2 parameters) at SD.LLBLGen.Pro.ApplicationCore.CodeGenerationMetaData.Tasks.Task.PerformElement(IGenerator executingGenerator, LogNode parentNode) at SD.LLBLGen.Pro.ApplicationCore.CodeGenerationMetaData.Tasks.TaskGroupElement.Perform(IGenerator executingGenerator, LogNode parentNode) at SD.LLBLGen.Pro.ApplicationCore.CodeGenerationMetaData.Tasks.TaskGroup.PerformElement(IGenerator executingGenerator, LogNode parentNode) at SD.LLBLGen.Pro.ApplicationCore.CodeGenerationMetaData.Tasks.TaskGroupElement.Perform(IGenerator executingGenerator, LogNode parentNode) at SD.LLBLGen.Pro.ApplicationCore.CodeGenerationMetaData.Tasks.TaskGroup.PerformElement(IGenerator executingGenerator, LogNode parentNode) at SD.LLBLGen.Pro.ApplicationCore.CodeGenerationMetaData.Tasks.TaskGroupElement.Perform(IGenerator executingGenerator, LogNode parentNode) at SD.LLBLGen.Pro.ApplicationCore.CodeGenerationMetaData.Tasks.TaskGroup.PerformElement(IGenerator executingGenerator, LogNode parentNode) at SD.LLBLGen.Pro.ApplicationCore.CodeGenerationMetaData.Tasks.TaskGroupElement.Perform(IGenerator executingGenerator, LogNode parentNode) at SD.LLBLGen.Pro.GeneratorCore.Generator.RunTasks(String rootNameSpaceToUse, String destinationRootFolder, String groupName) at SD.LLBLGen.Pro.GeneratorCore.Generator.Start(ITaskGroup tasksToExecute, ApplicationConfiguration configurationSettings, Language languageToUse, Platform platformToUse, List1 templateBindingsToUse, String templateGroupToUse, String rootNameSpaceToUse, String destinationRootFolder, Project projectDefinition, CodeGenerationCycleOutputType outputType) at SD.LLBLGen.Pro.GeneratorCore.Generator.Start(ITaskGroup tasksToExecute, CodeGenerationCyclePreferences preferences, ApplicationConfiguration configurationSettings, Project projectDefinition) at SD.LLBLGen.Pro.Gui.Classes.GuiController.PerformRunCodeGenerationCycleAction(ITaskGroup toExecute, CodeGenerationCyclePreferences codeGenerationCyclePreferences, HashSet1 entitiesToUse, HashSet1 spCallsToUse, HashSet1 typedViewsToUse, HashSet1 typedListsToUse, HashSet1 valueTypesToUse, HashSet1 tvfCallsTouse, List`1 vsNetProjectsCreated, LogNode& tasksResultLog)

Do you have attributes, special metadata, etc on you entities? In order to analyze this, it would be helpful if you open a HelpDesk thread (which is private) and upload your LLBLGen project).

Also, do you specific presets or vs.net project templates? Do you have filenames in tasks which are not replaced properly? (please check on disk)

I am pretty sure this is a template problem. It can be reproduced in other machines running the code gen. Thank you. I will try to look through the template and see where it may go wrong.

It goes wrong with creating the VS.NET project file, so the main issue is located in the preset used, as there you formulate the file/folder names, and I think you specified something which didn't get replaced (e.g. [entityName] instead of [elementName]), so then e.g. [entityName] is in the filename and this then placed into the xml of the vs.net project, causing the problem. You can check this by using the vanilla presets which we ship with the installer (which should work)