Home
Help
Register
Log in

Search

 
   Active Threads  

You are here: Home > LLBLGen Pro > Bugs & Issues> Error generation Base Classes Only
 

Pages: 1
Bugs & Issues
Error generation Base Classes Only
Page:1/1 

  Print all messages in this thread  
Poster Message
bonder
User



Location:

Joined on:
23-Sep-2003 05:05:17
Posted:
36 posts
# Posted on: 24-Jan-2004 03:24:40.  
Object reference not set to an instance of an object.

-----[Core exception]--------------------
at SD.LLBLGen.Pro.TDLInterpreter.Interpreter.HandleSingleTokenStatement()
at SD.LLBLGen.Pro.TDLInterpreter.Interpreter.HandleNonTerminal()
at SD.LLBLGen.Pro.TDLInterpreter.Interpreter.InnerLoopHandler()
at SD.LLBLGen.Pro.TDLInterpreter.Interpreter.HandleInputParameterLoopStart()
at SD.LLBLGen.Pro.TDLInterpreter.Interpreter.HandleNonTerminal()
at SD.LLBLGen.Pro.TDLInterpreter.Interpreter.InnerLoopHandler()
at SD.LLBLGen.Pro.TDLInterpreter.Interpreter.HandleActionStoredProcedureCallLoopStart()
at SD.LLBLGen.Pro.TDLInterpreter.Interpreter.HandleNonTerminal()
at SD.LLBLGen.Pro.TDLInterpreter.Interpreter.Interpret(StreamWriter outputStream)
at SD.LLBLGen.Pro.TaskPerformers.CodeEmitter.Perform(IGenerator executingGenerator, ITask taskDefinition, Hashtable parameters)
at SD.LLBLGen.Pro.GeneratorCore.Task.Perform(IGenerator executingGenerator)
at SD.LLBLGen.Pro.GeneratorCore.TaskGroup.Perform(IGenerator executingGenerator)
at SD.LLBLGen.Pro.GeneratorCore.TaskGroup.Perform(IGenerator executingGenerator)
at SD.LLBLGen.Pro.GeneratorCore.Generator.Start(ITaskGroup tasksToExecute, Project projectDefinition, TemplateSetDefinition templateSet, ApplicationConfiguration configurationSettings)
at SD.LLBLGen.Pro.Gui.Forms.MainWindow.StartGeneratorProcess()

SD.LLBLGen.Pro.TDLInterpreter
  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37405 posts
# Posted on: 24-Jan-2004 10:16:50.  
I've seen this one too here, and what I found out is the following:
This is caused by the fact that 2 months ago a bug was introduced which didn't save type information for stored procedure parameters correctly.

Refresh the catalog and it should be over. You'll get also an exception now if you edit the stored proc's properties.

THe bug was quickly fixed but it seemed some projects which were refreshed/created with that version are still carrying along the empty type information for the stored proc parameters.

If refreshing the catalog / regeneration of the code still gives the same results, it's something else, however it looks very familiar.


Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
bonder
User



Location:

Joined on:
23-Sep-2003 05:05:17
Posted:
36 posts
# Posted on: 24-Jan-2004 18:44:22.  
Thanks for the hint. I am pushing out a release of the software right now, so I will test this out after that and post my results back here. Hopefully then you can just mark this whole thing closed.

  Top
Coral
User



Location:
Cairns, Australia
Joined on:
28-Jan-2004 06:02:36
Posted:
3 posts
# Posted on: 28-Jan-2004 06:08:40.  
I have just had this same error, after installing latest version to fix error where it was generating duplicate functions. Refreshing the catalog, then regenerating code fixed the problem. Regular Smiley

  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37405 posts
# Posted on: 28-Jan-2004 08:28:44.  
It's a nasty one, with the gui updates I have to update the serialization code anyway, I'll see what I can do to inform the user about the absense of type information for stored proc parameters..
Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
Pages: 1  


Powered by HnD ©2002-2007 Solutions Design
HnD uses LLBLGen Pro

Version: 2.1.12172008 Final.