i came up with a carzy bug last week, in OneClick deployment CurrentDeployment.UpdateLocation.AbsoluteUri always return a cached url ??? it passes first time passed parameters back again and again when you run the application . so always use the ApplicationDeployment.CurrentDeployment.ActivationUri insted of UpdateLocation.AbsoluteUri.
if you are getting a null issue in CurrentDeployment.ActivationUri that means you have not set the application publish->options allow parameters option
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment