strange error: could not be set on property AdapterTypeName

Posts   
 
    
s-man
User
Posts: 2
Joined: 27-Sep-2006
# Posted on: 05-Oct-2006 17:10:04   

After dropping the llblgenpro datasource control on a form, switching to the Source and back to the design showed this error:

Error 1 Content1:'mypackage.DatabaseSpecific.DataAccessAdapter, mypackage.packageDBSpecific' could not be set on property 'AdapterTypeName'. C:\Documents and Settings\Stijn\Mijn documenten\Visual Studio 2005\WebSites##########.aspx C:...####2\

What i did before what often regenerate my code, maybe it has something to do with that. Tough, i can run my website withouth any problem, but it lacks design support right now.

Anyone experienced the same error, did I do something wrong over here?

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39588
Joined: 17-Aug-2003
# Posted on: 05-Oct-2006 18:22:04   

One of the VS.NET 2005 issues Microsoft hasn't provided a fix for...

Close the form, eventually build, then load the form in HTML, switch to design view and it should work. If it doesn't, close all forms, close solution, close vs.net, restart vs.net load solution, BUILD in full, load form in html, switch to designer.

It's so utterly strange why this happens, a lot of the datasource control writers run into this same problem. Lhotka of CSLA.NET found out that it seems to relate t temp assemblies vs.net creates behind the scenes... Though it's very odd, we had two dev systems, both had the same solution open, one could open the designer of a datasourcecontrol while the other kept the error, no matter what.

Frans Bouma | Lead developer LLBLGen Pro
s-man
User
Posts: 2
Joined: 27-Sep-2006
# Posted on: 07-Oct-2006 12:22:49   

thank you that worked!

El Barto
User
Posts: 64
Joined: 09-Nov-2006
# Posted on: 22-Jan-2007 10:48:59   

One day I started VS and suddenly I got this error. As far as I know I didn't make any changes in VS or in LLBLGen the previous day. I just wrote some code.

Since then I tried all sorts of things to solve this problem. I've tried the solutions on this forum, repaired my installation of VS, removed all the files in the .Net framework temp directory, removed my profile, remove and reinstall LLBLGen, searched for all LLBLGen.Pro DLL's and remove them all.

None of these have solved the problem. As far as I have read the posts on this forum and blogs on the internet, the problem is that VS loads a wrong version of the DLL. I know this forum is not the right place to ask, but has somebody have an other explanation on why this error pops up and a solution to this?

Thanks

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39588
Joined: 17-Aug-2003
# Posted on: 22-Jan-2007 11:33:39   

I saw that VS.NET 2005 SP1 (yes, the SP1 with that horrible installer) fixed this problem. Do you have SP1 for vs.net 2005 installed?

Frans Bouma | Lead developer LLBLGen Pro
El Barto
User
Posts: 64
Joined: 09-Nov-2006
# Posted on: 22-Jan-2007 14:59:39   

Sorry, forgot it in the list of things I tried. It's actualy the first thing I've tried without any luck.

Another project I'm working on works fine (so far). So I was wondering it maybe has to do something with the web.config. But I can't find any entries in the web.config that refer to ORMSupport DLL.

jbb avatar
jbb
User
Posts: 267
Joined: 29-Nov-2005
# Posted on: 22-Jan-2007 15:34:20   

Hello,

did you try to create a new project/solution in visual studio an copy/paste your files into it?

El Barto
User
Posts: 64
Joined: 09-Nov-2006
# Posted on: 24-Jan-2007 15:31:04   

I copied the complete solution to my laptop. On my laptop I got the same error. So I think that the solution to renew the solution/project files has a pretty good chance.

So that will be my next step, I'll post the result here when I come around to do it.

El Barto
User
Posts: 64
Joined: 09-Nov-2006
# Posted on: 29-Jan-2007 10:26:43   

Recreating the solution didn't work, but ditching the projectfiles of the DB specific en DB generic projects and regenerating the project worked.

Thanks.....