Data at the root level is invalid

Posts   
 
    
Fishy avatar
Fishy
User
Posts: 392
Joined: 15-Apr-2004
# Posted on: 05-Jun-2014 23:38:22   

Hi,

I'm getting the following error: Data at the root level is invalid. Line 1, position 1.

The Stack Trace: LLBLGen Pro version 4.1. Build May 16th, 2014 -----[Core exception]-------------------- at System.Xml.XmlTextReaderImpl.Throw(String res, String arg) at System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace() at System.Xml.XmlTextReaderImpl.ParseDocumentContent() at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace) 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.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)

NOTE: the Log Viewer does not show any errors.

Should I be concerned about this?

daelmo avatar
daelmo
Support Team
Posts: 8245
Joined: 28-Nov-2005
# Posted on: 06-Jun-2014 07:46:57   

Hi Fishy,

  • Does this happen after you migrate from an older version? Or some other info you could give us to identify the problem.

  • Does the exception stops the project load? Or maybe you can save it afterwards.

  • Also it would be helpful if you open a HelpDesk thread to attach your project there so we can take a look at it.

David Elizondo | LLBLGen Support Team
Fishy avatar
Fishy
User
Posts: 392
Joined: 15-Apr-2004
# Posted on: 06-Jun-2014 16:33:36   

It occured when I was generating source code. But, the problem has seemed to fix itself confused Perhaps closing and reopening the project did something.

Thanks

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39588
Joined: 17-Aug-2003
# Posted on: 06-Jun-2014 18:18:51   

Can I close this thread as 'solved'?

Frans Bouma | Lead developer LLBLGen Pro
Fishy avatar
Fishy
User
Posts: 392
Joined: 15-Apr-2004
# Posted on: 06-Jun-2014 18:23:21   

Sorry, I forgot that I can mark it Complete.

Fishy avatar
Fishy
User
Posts: 392
Joined: 15-Apr-2004
# Posted on: 10-Jun-2014 23:39:26   

Well, I thought this had fixed itself but I was wrong. I'm still getting the folloing error when I generate a 4.1 project that was converted from 2.6:

LLBLGen Pro version 4.1. Build May 16th, 2014
-----[Core exception]--------------------
   at System.Xml.XmlTextReaderImpl.Throw(String res, String arg)
   at System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace()
   at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
   at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
   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, Dictionary`2 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.GeneratorCore.Generator.RunTasks(String rootNameSpaceToUse, String destinationRootFolder, String groupName)
   at SD.LLBLGen.Pro.GeneratorCore.Generator.Start(ITaskGroup tasksToExecute, ApplicationConfiguration configurationSettings, Language languageToUse, Platform platformToUse, List`1 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, HashSet`1 entitiesToUse, HashSet`1 spCallsToUse, HashSet`1 typedViewsToUse, HashSet`1 typedListsToUse, HashSet`1 valueTypesToUse, HashSet`1 tvfCallsTouse, List`1 vsNetProjectsCreated, LogNode& tasksResultLog)

It generates the DatabaseGeneric folder and files but not the rest.

I've attached the project file.

Any help would be greatly appreciated.

Attachments
Filename File size Added on Approval
ConvertedProjectV40Format.llblgenproj 231,403 10-Jun-2014 23:39.39 Approved
Otis avatar
Otis
LLBLGen Pro Team
Posts: 39588
Joined: 17-Aug-2003
# Posted on: 11-Jun-2014 09:21:36   

looks like a bug in the 2008 project file template for vb.net, we'll look into it.

Frans Bouma | Lead developer LLBLGen Pro
Otis avatar
Otis
LLBLGen Pro Team
Posts: 39588
Joined: 17-Aug-2003
# Posted on: 11-Jun-2014 09:32:28   

Found it. A bad character was present in the file. I've attached the proper file. Please copy the file over the current one into the folder: <llblgen pro installation folder>\Frameworks\LLBLGen Pro\Templates\SharedTemplates\Net3.5\VB.NET

as Administrator

I also checked why we missed this, as we have automated tests which run several projects through the designer, generate code for c# and vb.net and compile them, and we missed this because we generate the code for .NET 4, not .NET 3.5, so our tests picked up the vs.net 2010 project file format.

Attachments
Filename File size Added on Approval
vsnet2008ProjectFileAdapter.template 3,946 11-Jun-2014 09:32.42 Approved
Frans Bouma | Lead developer LLBLGen Pro
Fishy avatar
Fishy
User
Posts: 392
Joined: 15-Apr-2004
# Posted on: 11-Jun-2014 16:19:41   

It worked! Thanks.