1. Home
  2. LLBLGen Pro
  3. LLBLGen Pro Runtime Framework

Very simple LLBLGenDataSource question...

Posts   
 
    
MattWoberts
User
Posts: 497
Joined: 08-Apr-2004
# Posted on: 23-Aug-2007 17:38:27   

Hi,

I think I'm having one of those "late afternoon" moments...

For some reason I can't get an LLBLGENDataSourceAdapter to work on my page - more specifically, I can't set a "AdapterTypeName" to anything! Its always a blank dropdown with nothing to choose...

I have tried creating a new web project. I then add a reference to SD.ORMSupportClasses (2.0), and to my 2 generated assemblies (I'm using Adapter). I then drag an LLBLGenDataSource onto my page, and try to use the designer to set the LLBLGenDataSource up. I tried setting the AdapterTypeName manually like this:

        <llblgenpro:LLBLGenProDataSource2 ID="LLBLGenProDataSource2_1" runat="server" DataContainerType="EntityCollection" AdapterTypeName="Company.DAL.GeneratedDBSpecific.DataAccessAdapter, Company.DAL.GeneratedDBSpecific">
        </llblgenpro:LLBLGenProDataSource2>

And this just causes it to complain when I switch back to the designer - with this error:

LLBLGenProDataSource2_1:'Company.DAL.GeneratedDBSpecific.DataAccessAdapter, Company.DAL.GeneratedDBSpecific' could not be set on property 'AdapterTypeName'. C:....Default.aspx

I have used these previously for a different project, so its not a LLBLGen Setup issue as far as I can tell....

Thanks in advance for any kind souls out there!

MattWoberts
User
Posts: 497
Joined: 08-Apr-2004
# Posted on: 24-Aug-2007 08:47:22   

Anyone?

Walaa avatar
Walaa
Support Team
Posts: 14950
Joined: 21-Aug-2005
# Posted on: 24-Aug-2007 09:27:38   

Please make sure the ORMSupport....dll used in the toolbox to add the LLBLGenProDataSource controls is exactly the same one referenced by your application. (version and path)

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39614
Joined: 17-Aug-2003
# Posted on: 24-Aug-2007 18:31:49   

Also, check if the generated code project is referenced from the webapp (this sounds stupid, but it's some small detail which is often overlooked). Also, vs.net 2005 contains some bugs in this area, which were mostly solved by SP1 for vs.net 2005.

Frans Bouma | Lead developer LLBLGen Pro
MattWoberts
User
Posts: 497
Joined: 08-Apr-2004
# Posted on: 28-Aug-2007 10:18:47   

Hi,

Thanks for the advice - but I still can't get it to work - this is driving me mad! Here's what I have just tried without success:-

  • Started LLBLGen 2.0 (December 6th build). Created a new Project, added a single table.
  • Generated code. Chose Adapter, target .NET 2.0, SQLServer bindings.
  • Opened VS.NET 2005 SP1. Created a new "ASP.NET Web Application".
  • Added existing project - chose both the Generated and the GeneratedDBSpecific project.
  • Noted that both these projects reference the ORMSupport..dll from my C:\Program Files\Solutions Design\LLBLGen Pro v2.0\RuntimeLibraries\DotNet20\SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll folder
  • Added a reference to my web application project - browsed to "C:\Program Files\Solutions Design\LLBLGen Pro v2.0\RuntimeLibraries\DotNet20\SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll"
  • Look at my toolbox "Choose Items..." Note that the LLBLGENDataSource2 comes from the ORMSupport DLL that is in the same place - "C:\Program Files\Solutions Design\LLBLGen Pro v2.0\RuntimeLibraries\DotNet20"
  • Create a new web form, and drag the LLBLGenDataSource2 object onto the page.
  • There are no entries in the DataAccessAdapter dropdown :-(

Please help me!!!

Walaa avatar
Walaa
Support Team
Posts: 14950
Joined: 21-Aug-2005
# Posted on: 28-Aug-2007 10:38:43   

Follow with the following steps: - Re-build the solution. - Close the webForm - Close VS - Re-open the VS. - Re-open the webForm. - Cross your fingers.

MattWoberts
User
Posts: 497
Joined: 08-Apr-2004
# Posted on: 28-Aug-2007 10:41:25   

I tried everything you said (although I must admit i didn't cross my fingers), and it didn't work rage

Walaa avatar
Walaa
Support Team
Posts: 14950
Joined: 21-Aug-2005
# Posted on: 28-Aug-2007 11:18:06   

I'm sorry to hear about that, I can't reproduce it right now, although it happened to me before, and instead of closing everything and re-openning them again, I usually wrote the needed information directly in the aspx files.

I know that's not the best thing to do, but it is a VS 2005 issue, and we have no control over it.

MattWoberts
User
Posts: 497
Joined: 08-Apr-2004
# Posted on: 28-Aug-2007 11:27:57   

When you say you wrote eveything into the aspx file - what exactly do you mean? Any way to get it to work will be a step forwards - and I can't get anything to work :-(

Walaa avatar
Walaa
Support Team
Posts: 14950
Joined: 21-Aug-2005
# Posted on: 28-Aug-2007 11:31:54   

Like this:

<llblgenpro:llblgenprodatasource2 ID="CustomersDS" runat="server"           
AdapterTypeName="SD.LLBLGen.Pro.Examples.DatabaseSpecific.DataAccessAdapter, SD.LLBLGen.Pro.ExamplesDBSpecific" 
DataContainerType="EntityCollection"            
EntityFactoryTypeName="SD.LLBLGen.Pro.Examples.FactoryClasses.CustomerEntityFactory, SD.LLBLGen.Pro.Examples" 
EnablePaging="True" 
AllowDuplicates="False">
</llblgenpro:llblgenprodatasource2>
MattWoberts
User
Posts: 497
Joined: 08-Apr-2004
# Posted on: 28-Aug-2007 12:03:04   

Ahh - thanks!

I tried doing that, and it was complaining about the DataAccessAdapter I was trying to set... This time, I manually added it to the ASPX - saw it complain - closed VS.NET, re-opened VS.NET, and it was working simple_smile

Thanks very much for your assistance, I re-learnt the old Microsoft mantra today:

If it doesn't work - close everything down and then try again!

wink