Windows 7 + vs10 Silverlight project upgrade [failed yesterday]

I don't know what happened to me yesterday. Please refer to yesterday.ArticleThank you.

 

Fault review:

Installed a great and beautiful win7

 

And installed vs 05, and later:

The problem of updating Silverlight project crashes or loops occurs.

 

Solve the problem today .. But it's silly. Even if it's silly, it's still hitting the nail!

 

The only solution is to create a project and import it one by one, which is common to developers .. I will not go into detail later. However, if you have servers, please note the following:

 

It must be set according to the server's aspx bearer version. Do not default to. net4.0. Otherwise, an MS. CSHARP library will be automatically loaded -- 3.5 seems to have no grace.

 

It is worth mentioning that: (I may not have read 08, but it is very user-friendly)

You can select the target version of Silverlight. Unlike the force upgrade of 08 + sl3beta, you can select a more stable 2.0 for development. This can be considered IF 08 has not yet entered 3.0.

 

If you directly use webapp (hold Silverlight) and SLProgramLoad them separately recently. You can connect them with this one. There is one in 08. Just put it up. Don't forget to set the build order and dependency.

 

If there are a lot of errors during the loading of WCF, it is basically a reference problem. It is better to let vs generate a reference list by itself. So first add a Silverlight enabled WCF -- call temp, and then delete it, And the ref will be done well.

From to 10, the WCF can be properly generated, but it cannot be used. A Not Found error occurs on the SL end. Very angry and untempered. After tracing for half a day, I found that the Silverlight enabled WCF of vs10 has changed a bit:

Is the binding settings in his web. config:

From basichttpbinding to custombinding, connect to a built-in SL binding of. It looks good, but it actually adds trouble to our old users,

 

For example, my Serivce is manually connected as follows:

 

SLC = new seloginclient (New basichttpbinding (), new endpointaddress ("http: // localhost: 11111/demo. SVC "));

 

But I noticed that the basichttpbinding has been exile .. it cannot be reused, and custom binding cannot be used, so I tried to change the web. config to the original look, delete custombinding, switch to basichttpbinding, and all the results will be restored-the world is quiet.

 

After being added one by one and modified .. My project finally broke through and broke into the bid ..

 

----- The project starts normal test ---- Cut a few pictures and put them up... I have been doing this for more than a year ..

Loading

In this process, I also experienced a powerful test function of Vs, and even the event was fully monitored .. No worries

 

 

By the way, I forgot to say that I would like to develop duplex or say that I would like to thank my comrades in D-factory. Do not forget to modify ASP compatibility in Web. config so that I can run nun only when it reaches false.

 

 

 

Applink function .. Hard work

 

So much, the upgrade method is the focus .. The final image is used for flushing .. Ignore...

 

 

I am a newbie .. A little smile ..