LLBLGen 3 startup issue

Posts   
 
    
MattE avatar
MattE
User
Posts: 77
Joined: 11-Sep-2007
# Posted on: 08-Sep-2010 10:45:50   

Hi there,

I've just upgraded to 3 and get the exception below: when trying to run the IDE

I've added my license file a the root as LLBLGenPro3_1.license

I've seen some posts about deleting guistate and preferences . xml but can't find them in this build?

THanks,

Exception information.

LLBLGen Pro version: v3.0. Build: August 30th, 2010

Exception details:

Message: Data at the root level is invalid. Line 1, position 1. Source: System.Xml Stack trace: at System.Xml.XmlTextReaderImpl.Throw(Exception e) 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.Load(String filename) at ab.a(String A_0, DateTime A_1, Int64 A_2, String A_3) at k..ctor(Assembly A_0, String A_1, String A_2, String A_3, Boolean A_4) at ActiproSoftware.SyntaxEditor.Addons.DotNet.Dom.AssemblyCodeRepository.a.a(c A_0) at ActiproSoftware.SyntaxEditor.Addons.DotNet.Dom.AssemblyCodeRepository.Add(Assembly assembly, String assemblyFullName, DotNetProjectResolver projectResolver) at ActiproSoftware.SyntaxEditor.Addons.DotNet.Dom.DotNetProjectResolver.AddExternalReference(Assembly assembly, String assemblyFullName) at ActiproSoftware.SyntaxEditor.Addons.DotNet.Dom.DotNetProjectResolver.AddExternalReference(Assembly assembly) at ActiproSoftware.SyntaxEditor.Addons.DotNet.Dom.DotNetProjectResolver.AddExternalReferenceForSystemAssembly(String assemblyName) at SD.LLBLGen.Pro.Gui.Classes.GuiState.InitializeProjectResolver() at SD.LLBLGen.Pro.Gui.Program.DoApplicationStart(String fileToLoad)

Inner exception: <null>

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39613
Joined: 17-Aug-2003
# Posted on: 08-Sep-2010 10:59:28   

It's not the license, it's a control we use for the editor. Did you add anything to the TypeConverters folder ? Did you change anything after the install or did you just store the license file and that's it?

You have .net 3.5 installed or only net 4.0 ?

Frans Bouma | Lead developer LLBLGen Pro
MattE avatar
MattE
User
Posts: 77
Joined: 11-Sep-2007
# Posted on: 08-Sep-2010 11:11:50   

Clean install, nothing added to TypeConverters folder

I just dropped in the license file

I'm running Windows 7 64 bit, with both .Net 3.5 and 4 installed.

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39613
Joined: 17-Aug-2003
# Posted on: 08-Sep-2010 11:28:33   

It happens in one of these lines: _projectResolver.AddExternalReferenceForSystemAssembly("System.Core"); _projectResolver.AddExternalReferenceForSystemAssembly("System.Data.Linq"); _projectResolver.AddExternalReferenceForSystemAssembly("System.Xml"); _projectResolver.AddExternalReferenceForSystemAssembly("System"); _projectResolver.AddExternalReferenceForSystemAssembly("System.Data");

so I think one of the .xml files for these assemblies is corrupt in your .NET install. Could you please check which one? They're located in the folder

C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5

(the system assembly doesn't have a .xml file apparently, can't find it).

opening the .xml file in notepad or firefox should be enough to see what the problem is. If they're all OK, please let me know so I can report to actipro software that something weird is going on.

Btw, the trial worked as expected? (same code)

Frans Bouma | Lead developer LLBLGen Pro
MattE avatar
MattE
User
Posts: 77
Joined: 11-Sep-2007
# Posted on: 08-Sep-2010 12:04:46   

That folder only contains binaries, no XML files at all.

I never ran the trial to answer your question. Just bought the license, downloaded and installed v3 and copied in the license.

Thanks,

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39613
Joined: 17-Aug-2003
# Posted on: 08-Sep-2010 12:38:35   

I sent you a hotfix for the issue, which means I wrapped the calls in a try/catch so the error doesn't pop up. Not sure if this fixes it, it's very odd that this happens. Either way I think it's also a good idea to do a repair install of vs.net or the .net sdk if you have that installed.

Frankly I don't know why the exception pops up, the try/catch wrapping might stop it at least. Of course you won't have the intellisense of that namespace in the editor, but that's rather minor. If you don't receive it or it crashes somewhere else, please let me know

Frans Bouma | Lead developer LLBLGen Pro
Otis avatar
Otis
LLBLGen Pro Team
Posts: 39613
Joined: 17-Aug-2003
# Posted on: 08-Sep-2010 13:28:07   

Wrapping the calls in try/catch makes the designer start at least. Reported with actipro software.

Frans Bouma | Lead developer LLBLGen Pro