Can't load Csla in wpf designer?

Can't load Csla in wpf designer?

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

ajj3085 posted on Thursday, December 20, 2007

I'm trying to add a CslaDataProvider to my wpf control and the designer insists it can't find Csla.

Could not load file or assembly 'Csla, Version=2007.12.20.3, Culture=neutral, PublicKeyToken=74bfa51f58c67f0e' or one of its dependencies. The system cannot find the file specified.


Any ideas?

RockfordLhotka replied on Thursday, December 20, 2007

This is in VS08? I've done a lot of this with no problem.

Well, no problem as long as I got the xmlns line right so the namespace was imported properly - that is easy to mis-type. That XML typo issue has been my single biggest problem with WPF programming because you get no intellisense on those xlmns lines.

ajj3085 replied on Friday, December 21, 2007

Yes, 2008 Pro RTM.  I've deleted and retyped the line... maybe I'll copy and paste it from PTracker, which seems to work.

Could there be a problem because my reference points to a mapped network drive?  Copy Local is set to true though, and nothing else has a problem with the assembly refering to that location.

I'll try some things and see.

RockfordLhotka replied on Friday, December 21, 2007

It could be the network drive. Remember that .NET treats network drives like they are part of the Intranet, and so files from those locations aren’t trusted.

 

Rocky

 

 

From: ajj3085 [mailto:cslanet@lhotka.net]
Sent: Friday, December 21, 2007 9:06 AM
To: rocky@lhotka.net
Subject: Re: [CSLA .NET] Can't load Csla in wpf designer?

 

Yes, 2008 Pro RTM.  I've deleted and retyped the line... maybe I'll copy and paste it from PTracker, which seems to work.

Could there be a problem because my reference points to a mapped network drive?  Copy Local is set to true though, and nothing else has a problem with the assembly refering to that location.

I'll try some things and see.


ajj3085 replied on Friday, December 21, 2007

I found the problem; I copied the Csla assembly to my desktop and referenced it in my project, and it works fine.  Everything else works from the network location, so I'm a bit suprised the designer isn't.  I guess my next step is to try to get .Net to trust that location via IE's trusted sites, or the .Net 2 control panel.

ajj3085 replied on Friday, December 21, 2007

Here's the fix; just use the .Net 2.0 Configuration snap-in to specifically trust that assembly on the network drive.

I tried adding the drive to IE's trusted site, and having .Net trust fully all Trusted sites, but instead of file:///r:/* it would change it to file:////dev_server.  Grr. 

Fixed now though.

Copyright (c) Marimer LLC