Powered by Passion

In your silverlight application if can see the error. It may also arise after get latest from the source safe control. No need to worry just set up as start up page of your web ASPX file.

1. Rename your Silverlight application as you want to give the assembly name of your application. 2. Right click on the project -> properties -> Silverlight  rename the same as you give first on the red marking only. 3. Click on assembly also rename here only marking 4. Buid the project. if you run it you will get error. becoz the aspx file now running the previous xap file. so you must also have to rename as your newly assembly file/xap file in the aspx file as following figure. Now build & run you application.

After migrating a Silverlight application in VS-2012, our existing service is not exposed in VS-2012. Or if we create a new Silverlight application in VS-2012 and want to use the existing service in new application then our existing service will not exposed in VS-2012. We can use existing service in VS-2012 Silverlight application by following the steps. 1.      1.  We have to open the application in VS-2010     1.       2. If you are using n tier project in your then many other project will not be show ( incompatible ). But this is not a problem. You just clean the Silverlight client application. 1.     3.  Expand the client project right click on Service References . Here it is important that if are using source control & if you have already ServiceReferences.ClientConfig file. Then it should also be check out & check that which service you ar...