Print Page | Close Window

IdeaBlade.EntityModel.Push.SL.dll does not get included in the xap on deploy

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=3685
Printed Date: 13-May-2026 at 2:59am


Topic: IdeaBlade.EntityModel.Push.SL.dll does not get included in the xap on deploy
Posted By: JohnBloom
Subject: IdeaBlade.EntityModel.Push.SL.dll does not get included in the xap on deploy
Date Posted: 02-Oct-2012 at 7:56am
This is a weird problem and I am really at a loss as to how it is happening. I recently added push to our application and it was really pretty simple. I had the coding done quickly and uploaded my code. 

I started getting reports from people of a runtime error on our build server's automatic deployment. 

I jumped on and the error message said this: "The assembly ‘IdeaBlade.EntityModel.Push.SL’ must be included in your XAP to use NotificationService from Silverlight. This assembly was not found."

I had seen this error in dev so I knew what the issue was. I had also fixed this error in dev and it was surprising to see it again. 

I went and looked at the main xap and sure enough it was not in there. I went to the project and copy local was set to true. I looked in my xap on my dev machine and it was it was there. So it was copying to the xap in dev but not in production.

This is the first issue I have had like this where a dll was not getting set in a xap even though copy local was set to true. I have been  putting this on the back burner and keep coming back to it hoping that after a little bit of time I will have an epiphany and see what is going on but no luck. 

I looked at the csproj file and the xml looks exactly like IdeaBlade.EntityModel with the Push.dll added. I also tried specific version and non specific version and it still didnt work. I tried setting my dev to build in release mode and no change.

Has anyone seen this before?


-------------
-John Bloom


Replies:
Posted By: JohnBloom
Date Posted: 03-Oct-2012 at 6:59am
So I am assuming that this is not something people have run into. I am narrowing down the problem and I think it is related to the fact that I dont have devforce installed on the build server. We reference the dlls from subversion. It seems that push might have a dependency on something that is not in the main dlls. 

This guy had a similar problem: 
http://www.jiffnotes.com/2012/04/05/AssemblyImplicitReferencesInstallationsAndTheMSBuildImpact.aspx - http://www.jiffnotes.com/2012/04/05/AssemblyImplicitReferencesInstallationsAndTheMSBuildImpact.aspx


-------------
-John Bloom

Posted By: JohnBloom
Date Posted: 03-Oct-2012 at 7:10am
I confirmed that duplexing dlls in the C:\Program Files (x86)\Microsoft SDKs\Silverlight\v4.0\Libraries exist on the build server. I also copied the devforce install directory over to the build server in case it happened to be looking there for a dll and I am still having the problem.

-------------
-John Bloom

Posted By: sbelini
Date Posted: 03-Oct-2012 at 10:45am
Hi John,
 
Sorry for the late reply.
Our guess is that because IdeaBlade.EntityModel.Push.SL is referenced dynamically, when you do a build in Release Mode it simply won't be included in the XAP.
 
I am running some tests to confirm if this is actually the case and how to ensure the assembly is included in the client.
 
Silvio.

Posted By: sbelini
Date Posted: 04-Oct-2012 at 12:58pm
John,
 
I haven't been able to reproduce the issue here.
In your build log, have you spotted anything that could lead to it? (i.e. /verbosity:diagnostic)
You mentioned that you copied the devforce install directory over to the build server. Did you try installing DevForce?
 
Silvio.

Posted By: rharrington
Date Posted: 05-Oct-2012 at 6:07am
Silvio,

I am working with John and we don't want to put visual studio on the build machine but we will try and get you a sample app.

Regan

Posted By: sbelini
Date Posted: 08-Oct-2012 at 12:41pm
Hi Regan and John,
 
I did some research and found this article at http://stackoverflow.com/questions/3065576/assembly-reference-in-silverlight-class-library-and-used-only-in-xaml-is-not-pac - http://stackoverflow.com/questions/3065576/assembly-reference-in-silverlight-class-library-and-used-only-in-xaml-is-not-pac  that provided a way to circunvent the problem.
Since I couldn't reproduce the problem, I couldn't test it, but you might want to give it a try.
 
Let me know if this helps,
   Silvio.


Print Page | Close Window