DevForce 2010: Error on Server after updating to 6.0.8

Error on Server after updating to 6.0.8

Printed From: IdeaBlade
Category: DevForce
Forum Name: DevForce 2010
Forum Discription: For .NET 4.0
URL: http://www.ideablade.com/forum/forum_posts.asp?TID=2472
Printed Date: 12-Apr-2026 at 7:22pm

Topic: Error on Server after updating to 6.0.8

Posted By: BillG
Subject: Error on Server after updating to 6.0.8
Date Posted: 28-Jan-2011 at 12:50pm

I installed 6.0.8. I rebuilt my Silverlight Client and my Web project. I rebuilt my Model. Everything works fine on my development machine. I can run it just fine and debug etc.

I copied the new Ideablade.dlls to the server and placed them in the bin directory. I copied the compiled .xap and placed it in the clientbin directory. I stopped and restarted the iis server.

I get this error when I log into the app

Unable to locate type: Ideablade.EntityModel.EntityServerException, IdeaBlade.EntityModel, Version=6.0.8.0, Culture=neutral, PublicKeyToken=287b5094865421c0

When I look at the log, this is the last entry.

Caught exception: System.Exception: Unable to locate type: IdeaBlade.EntityModel.EntityQueryProxy`1[[LaborWare2011.User, LaborWare2011, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null]], IdeaBlade.EntityModel.SL, Version=6.0.7.0, Culture=neutral, PublicKeyToken=287b5094865421c0. Check that the assembly holding this type is available in the bin/exe folder. Also check that both your

I have checked all my dlls on the server and they are 6.0.8 where is this coming from?

Bill

Replies:

Posted By: BillG
Date Posted: 28-Jan-2011 at 1:32pm

I also checked my .xap and it has the 6.0.8 IdeaBlade .dlls in it.

Posted By: kimj
Date Posted: 28-Jan-2011 at 6:50pm

The error messages indicate that the server is running 6.0.8 but the XAP is still using 6.0.7. The most likely cause of this problem - once you've ensured the XAP was built correctly, as you have - is that the browser has cached the XAP file and it's the old file which has been loaded.

There's much discussion of this issue in the Silverlight world; here's one thread on the SL forums - http://forums.silverlight.net/forums/t/11995.aspx - http://forums.silverlight.net/forums/t/11995.aspx , and google will bring up additional information.

There are a number of ways to ensure the XAP is not cached at all, or that a new XAP will be used when available. Possibly the easiest is to append either a version number or timestamp to the URL of the XAP. You can either hardcode the value or determine it via code.

Here's a simple example - change the object tag in the default.aspx to add a query parameter to the XAP URL:

</object>