Simple comparison between ASP. NET and Silverlight

Recently, ASP. NET is used as a simple website. There are not many pages, that is, adding, deleting, querying, and modifying some data. I don't need to worry about it for the artist.

When I went to school, I actually had my website or something, I had a blog system, and I had imitated some functions of kaixin.com. Using ASP. NET as a website is no stranger. After work, I have been using Silverlight. When I first learned it, I felt very simple. After I connected the database, I established the model. everything at the bottom was okay. I just needed to write some operations by myself, A year later, I used ASP. net website. Maybe I have no idea how powerful ASP. NET is.

1. ASP. net object class, I have to write it myself. I write 80 + fields in an order class one by one. Well, I know that software such as dynamic software can assist, but it is only for temporary use, I don't like to install these software on my computer. This shows how fast and convenient Silverlight is to build a model and build a domainservice.

2. Although there is no need to consider a lot of art, at least the interface I made looks neat. DIV is really flexible at times. I think that flexible things need to be well controlled, otherwise they will not get the desired effect. For an effect, I tried the N multi-attribute n multi-value of Div and did not see any changes at all. Finally, I had to use a rigid table to solve the problem. above, I prefer grid in Silverlight, it can also be scaled freely. Each control also has attributes such as minheight and maxheight.

3. I have a headache when binding data. I need to call a piece of data from the database and assign 80 + fields to the corresponding controls one by one. After the modification, I cannot know where the user has changed, so I have to assign the values of each control to my objects one by one. When data is written to the background, each field in the database is updated. Amount ...... I am not a diligent person. I prefer to bind a field to a control in Silverlight and bind an object to the container where the control is located. I only need to call the submit () method when saving the control, it will package the changes into a Changeset and upload them back for processing.

After talking about this, it only means that I am a relatively lazy person, and there are more than N differences. I still can't say it. In fact, I think Silverlight is better in terms of data processing, it packs a lot of things to reduce the occurrence of errors. If the packaged items are inappropriate, they can be modified. Generally, this change is rare. Silverlight can also make a lot of cool and dazzling things. I have never said that before.

Although it is said that the development of hardware and software is very fast, it is undeniable that there are still n users using the configuration a few years ago. Silverlight requires the IE8 kernel, the user's machine must be upgraded and assembled. ASP. NET is not required, but for developers, developers need to consider the effects of their websites on different browsers and perform tests repeatedly.

Each has its own advantages and you can choose one.