Hello all, I'm currently developing a full trust XBAP. I'm hosting the published release version of the XBAP on my Windows Azure storage account.
Recently, when I publish a new release version of the XBAP, some users receive a System.Deployment.Application.DeploymentException when trying to access the new version of the XBAP. The previous version of the XBAP worked on their computers no problem.
I did some research that suggest this exception may be caused if the version number of the XBAP is not incremented upon release. (I double checked, the release number IS automatically incremented). I also read I should use mage -cc to clear the cache
before building and publishing. I tried both of these solutions to no avail.
If a user receives this error I can get the XBAP to run on their computer if I manually delete the appdata/Local/Apps/2.0/Data... folder where the XBAP is cached.
So my question is, how can publishing a new version of the XBAP (with a properly incremented version number) cause the XBAP to stop working on a computer where the previous version ran without error? What could cause the need to delete the appdata/Local/Apps/2.0/Data...
folder where the XBAP is stored to fix the problem? And is there any way to ensure that this problem won't happen in the future?
Thanks for your help. The gory exception det
View Complete Post