LLBLGen Pro Support System General FAQ feed

My Retrieval Procedure is treated like Action Procedure at LLBLGen Pro Designer by daelmo

daelmo — Tue, 28 Feb 2012 01:38:08 GMT

For v3.x the solution is slightly different. There are two options:

A. Let LLBLGen to determine the resulset When refresh your relational model from database, there is a step where you can specify the stored procedures for which the resulset relational data model has to be determined. Select all SP's or just those you want that LLBGen automatically determines the resulset(s). For more info read Relational Model Data Retrieval Wizard.

B. Specify the number of resulsets manually. If you don't want to go on option (A), or if for some reason the resulset info can't be retrieved (i.e. too complex SP), you can specify the number of resulsets manually:

Open your .llblgenprojh file.
Expand the Catalog Explorer toolbar. This toolbar is generally placed at the right side of the LLBGen Designer.
Locate your stored procedure.
Right click at the SP node and click on 'Select Number of Resulsets' option, then select the appropriate number of resulsets (0, 1, 2 or more).

I can't open the LLBLGen Pro user or reference manual by Otis

Otis — Thu, 23 Jul 2009 08:46:41 GMT

See also the attached screenshot for unblocking the security settings for some situations.

My Retrieval Procedure is treated like Action Procedure at LLBLGen Pro Designer by daelmo

daelmo — Mon, 08 Dec 2008 03:24:18 GMT

Question: My retrieval stored procedure are treated like action procedure when refreshing the catalog at LLBLGen Pro Designer. How can I make it Retrieval Procedure?

Solution:

Open your .lpg file.
Expand the Catalog Explorer toolbar. This toolbar generally is placed at the right side of the LLBGen Designer.
Locale your stored procedure and expand it.
Expand the "Number of resulsets" node.
Right click at the "#0" node and click "Change value" option. Or press [F2].
Set the value to 1.

I can't register the v2.x reference manual in VS.NET 2008 by Otis

Otis — Tue, 11 Mar 2008 17:16:46 GMT

To register the .NET 2.0 reference manual in VS.NET 2008, open the RegisterHelp2.bat in a texteditor and change MS.VSIPCC.v80 in MS.VSIPCC.v90

Do this also in the UnRegisterHelp2.bat. After that, run RegisterHelp2.bat and the help should be available in the contents section of VS.NET 2008 help.

Missing namespaces by Aglaia

Aglaia — Tue, 21 Aug 2007 12:21:07 GMT

Question: When I compile the VB.NET code I generated with LLBLGen Pro, I get all kinds of errors about missing namespaces, what's wrong?

Solution: It is recommended that you use the generated Visual Studio.net project files. When you add the classes to a project you created manually, do not specify a 'Root namespace' in the VB.NET project properties in Visual Studio.NET, this name is also used as a prefix for namespace names in VB.NET. This name is filled in by default by Visual Studio.NET, so you have to clear that textbox manually. See the note in the LLBLGen Pro documentation: Using the designer / Generating Code, at the bottom.

Compiling a solution in release build fails by Aglaia

Aglaia — Tue, 21 Aug 2007 12:20:40 GMT

Question: I have generated C# code using the Adapter template group and added both the database generic and database specific projects to a solution. When I compile the complete solution in debug build, everything is fine, however when I compile the solution in release build, it fails. How's this possible?

Solution: Both projects, database specific and database generic, reference the ORM Support classes and have the 'copy local' setting set to true. This can give conflicts in some build modes. Set one of the references' copy local setting to false. You can also set the copy local setting of the reference in both projects to false and only set the copy local setting of the reference to the ORM Support classes in your main project to true. As long as the ORM support classes are present in the folder from where you start your application, it's fine.

My code won't compile when I use names similar to properties in the base class by Aglaia

Aglaia — Tue, 21 Aug 2007 12:20:15 GMT

Question: When I give a field mapped on a relation or a field in one of my entities a name similar to a property exposed in the base classes (for example 'Fields'), my code won't compile. How can this be?

Solution: All code generated by LLBLGen Pro, which thus contains your project specific names and values, in fact customizes generic code compiled into the ORMSupport classes. This means that if you name a field like 'Fields' it will be generated as a property 'Fields' in your entity class, and by that hide the Fields property of the EntityBase(2) class. This is by design. To work around this, rename your field so it won't clash with the property in the base class.

"The key 'Main.ConnectionString' does not exist" by Aglaia

Aglaia — Tue, 21 Aug 2007 12:18:46 GMT

Question: I've downloaded the demo application and generated code using the SqlServer demo database 'Northwind'. I wrote a simple ASP.NET application using the code but when I try to run that application, it throws an exception with the following error: "The key 'Main.ConnectionString' does not exist in the appSettings configuration section." What caused this error?

Solution: The generated code is a class library and is used in another program. The executable which ultimately is using the generated code (asp.net application, winforms application or console application), can be equiped with a .config file (web.config or app.config). LLBLGen Pro automatically generates a file called App.Config. This file contains a tag called . When you are using ASP.NET, you should copy that tag including its contents to the web.config file of your ASP.NET application and place it directly inside the tags. Now, the ASP.NET application has a definition of the Main.ConnectionString key and value and the generated code can read that key now to connect to the database. When you use winforms or a console application you can use the complete app.config file generated by LLBLGen Pro by adding it to the .exe project.

Deadlocks when using SSPI integrated security by Aglaia

Aglaia — Tue, 21 Aug 2007 12:18:16 GMT

Question: I use MSDE locally and with the default connection string generated, which uses SSPI integrated security I get deadlocks. What's the reason for this? ** Solution:** Some group policy lock downs of windows systems can cause deadlocks or even the fact that you can't log into your MSDE using SSPI security settings in your connection string. Try to use SqlServer security instead.

Missing buttons in the TypedList Editor. by Aglaia

Aglaia — Tue, 21 Aug 2007 12:17:22 GMT

Question: In the Typed List editor (opened by selected Edit/properties on a typed list) I can't find the Add / Remove buttons to add or remove an entity from my typed list. How to make these visible?

Solution: It's likely you have the Application Output window docked below the Typed List editor, which makes the TypedList editor to scale and hide the Add / Remove buttons with other controls. Please click the pin button on the Application Output window to hide it at the bottom of the designer. You can create extra space in the editors by disabling the little help bars at the bottom of the editors by setting the Preference 'ShowInScreenHints' to false. This requires to re-open an editor to take effect.