CSLA version 3.0 error when loggin in.

CSLA version 3.0 error when loggin in.

Old forum URL: forums.lhotka.net/forums/t/3911.aspx


elfstoneUK posted on Monday, November 19, 2007

Ladies and Gentlemen your help please.

In view of my databinding I've been advised to use CSLA version 3. So I downloaded, compiled and referenced the CSLA.DLL, which built with no errors. Ran the ProjectTrackervb as a test but got the following error when I login in:

Could not load type 'Csla.DataPortalClient.WcfProxy' from assembly 'Csla, Version=3.0.2.0, Culture=neutral, PublicKeyToken=93be5fdc093e4c30'.

in DataPortal.vb file.

Can anyone tell me what's wrong?

My system details:

VS 2005 (using VB) with SP1

OS - Windows XP SP2

.NET Framework 3.0 is installed but we are not using any WCF, WPF, etc at this time.

What is the significance of the WcfProxy in the error message?

BTW ProjectTrackervb for CSLA 2.1.4 works ok.

Thanks for reading

 

richardb replied on Monday, November 19, 2007

From memory I think if you are not using WCF or WPF you can remove those projects from the solution.  That or there are some DEBUG symbols that you can set to switch the .Net 3.x stuff on and off.

I haven't got the notes to hand but check Rocky's document about setting up CSLA and the demo projects - I'm sure I saw something in there about this.

richardb replied on Monday, November 19, 2007

Check you config file too to make sure you are using the right Dataportal channel.

elfstoneUK replied on Monday, November 19, 2007

richard ,

thanks for your reply. I do remember the article from Rocky and was going to change that but since this is the ProjectTrackervb demo, it already contains that Custom Constants setting set to NET20.

However, I didn't check the app.config for the

<add key="CslaDataPortalProxy" value="Csla.DataPortalClient.WcfProxy, Csla"/>

..found it and commented it out and it has cured my error. Smile [:)] Very pleased, thanks Richard.

Big Smile [:D]

Copyright (c) Marimer LLC