Skip to main content
Home Forums Silverlight Programming Visual Studio & Silverlight Development Tools Delay signing trouble.
4 replies. Latest Post by Sluser on February 27, 2009.
(0)
Kjell
Member
7 points
18 Posts
03-17-2008 2:55 AM |
Hi
I am trying to delay sign a silverlight app (2 beta 1).
I have checked the delay sign option in build properties.
After building I unzip the xap, resign the app, rezip it again and everything works as it should. I can deploy the app, refresh the page, run an iisreset and it all works.
However, if I click F5 again from VS2008 without changing anything (Nothing gets rebuilt, no build events are run), the Silverlight App crashes with Sys.InvalidOperationException: InitializeError #2105 in control 'Xaml1': Failed to load prerequisites for the application.
After that nothing can get it working again. If I look at "last updated", no files seem to have been updated with the F5 refresh. Still it obviously has broken something.
To get the app working again I need to Clean the solution and rebuild it again.
Anyone knows what is going on here?
/K
03-17-2008 5:57 PM |
Hmm it seems that VS2008 updates the .xap file every time I hit F5 even though it is not rebuilding anything.
Thus it will skip my resigning build steps and end up with a delay signed silverlight app in the .xap and a crash.
Even more annoying though is that I noticed that delay signed silverlight apps won't run, even if I register them with sn -Vr.
Anyone figure out how to run delay signed silverlight apps?
YugangW
100 points
25 Posts
03-25-2008 2:07 PM |
Hi,
I assume you have a post-build event which unpacks the .xap file, sign the .dll and repack the .xap file. Once the build is done, can you unpack the .xap file at the web site to confirm whether the .dll insider is signed correctly by running "sn.exe -vf <dll name>" ?
I don't think running "sn.exe -Vf" to skip the verification will work because the application runs inside the browser and it might not have privilege to access the information from the local system, but I will confirm with related product team.
Hope it helps.
Yugang
03-27-2008 6:20 PM |
I made an ugly temporary solution.
Last thing in the build I delete some object files forcing a recompile of the solution every time I build. This forces the compilation to redo my build steps every time and make sure I end up with a fully signed dll in the xap.
However I am guessing that what it does is that every time I hit F5, it replaces the .xap in the web application project with the .xap from the Silverlight project. Since I only resigned the dlls in the .xap in web application project I end up with getting the unsigned versions if I hit F5 without changing anything to the solution. Thus it should be fixable if I resign both the .xap in the web application directory, and the .xap in the silverlight project directory. But that is a test for another day.
/Kjell
Sluser
2 points
1 Posts
02-27-2009 2:03 PM |
Did you find out why verification skipping is not working?
Is there a work around to make delay signing and verification skipping work?
Thanks,
Siva