Problem with CSLA framework

Problem with CSLA framework

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


Jags posted on Monday, May 14, 2007

Hi everybody,

Our project solution is compiling good. But when I m running the application, we are getting an error like

 CS0006: Metadata file 'c:\windows\microsoft.net\framework\v1.1.4322\temporary asp.net files\longvtanks\b40c179c\6861d127\assembly\dl2\13d955fc\004fef80_7570c701\csla.server.dataportal.dll' could not be found

 When I am rebuilding the application, we are not getting this error and the application works fine. So whenever I am modifying the application I need to rebuild the application twice for successful execution.

 I have also compiled the csla framework by generating snk file and registered the dll file in GAC. We have also tried to solve this by searching in lot of URLs.

Advanced thanks for the sophisticated technical person who is gonna help me.

RockfordLhotka replied on Monday, May 14, 2007

As I said on your last post, I'm surprised it is trying to load the assembly from that path if you have it in the GAC.

Have you tried running the projecttracker sample app? Have you confirmed that your web server is set up property (runs aspx/asmx pages)? Have you tried a simple remoting "hello world" scenario to ensure remoting works properly at a basic level? You realize your web server is running .NET 1.1 - is that the version of .NET being used by your app?

This is not an error message I can recall anyone posting about before, which is probably why you aren't getting a lot of response. Have you searched www.searchcsla.com to see if someone did post about it years ago?

99.9999% of the time, the reason for remoting failures is due to IIS configuration, ASP.NET configuration, project reference, web.config or app.config errors (with config file typos being the biggest issue).

geordiepaul replied on Tuesday, May 15, 2007

Hi,

I have seen something similar to this. Have to tried deleting everything from your temporary asp.net files folder? I seem to remember that solved it for me. Must admit it wasn't a 1.1 issue so it may not solve your problem.

Paul

Copyright (c) Marimer LLC