1/7/2024 0 Comments Micro soft silverlight![]() ![]() Silverlight and Ajax Technologies Are Complementary The markup language is different, but the techniques are the same.ĥ. Normally, the header and footer (and often the left and right side borders) are reused throughout a webpage.īecause XAML is just markup, you can use server-side technologies to dynamically create XAML, just as your development teams already do with HTML. A good example is the design of the main page of most websites. This technique is so compelling because you can create reusable pieces of HTML that you use on your site. No matter what tools your developers use for server-side Web development, you are probably creating dynamic HTML to create pages. XAML being markup is important because it can be created dynamically. However, instead of the browser interpreting the instructions about how to render the file, the Silverlight runtime does the rendering. HTML files are plain text that contain information that tells the Web browser how to render the look and feel of a webpage. You may already be familiar with another popular markup language, HTML. XAML is the Silverlight’s Lingua Franca for user interface design. If your team is adept at client-side languages like JavaScript, Silverlight 1.0 is a great platform to introduce.Ĥ. If your development team primarily does heavy ASP.NET server-side development (mostly C# and VB.NET), you should wait until Silverlight 1.1 is available. The version of Silverlight you choose to introduce to a new project will likely depend on your development team’s skill set. Even if your developers lack these skills, learning these technologies has applicability beyond the single product or project-which isn’t necessarily the case for other solutions, such as Adobe Flash’s ActionScript. NET and Web technologies, they can use their existing knowledge to build Silverlight applications. If your developers are already familiar with Microsoft. Silverlight is built with existing Microsoft technologies: a mix of Windows Presentation Framework-like XAML (XML application markup language), JavaScript and. Silverlight Uses Technologies Your Developers Already Know The Silverlight 1.0 experience is much less mature and is unlikely to get third parties interested in control development.ģ. Silverlight 1.1 also supports a rich custom control model, which is important to ensure an integrated development experience. Silverlight 1.0 works well for existing Web developers who are already using client-side script for their work. In contrast, Silverlight 1.0 only supports ECMA languages that are interpreted in the client. NET language should be supported, since what is actually delivered to the browser are. NET developers to create interesting Silverlight applications. In my opinion, the important languages for Silverlight to support are C# and Visual Basic, as they allow current. ![]() NET support for dynamic languages, such as Ruby, Python, dynamic Visual Basic and managed JScript. In addition, according to Microsoft, Silverlight 1.1 will have. The Silverlight 1.1 release (currently in an Alpha preview) is the first to support. While Silverlight 1.0 has many important and interesting features, in reality most Silverlight adoption hangs on its anticipated 1.1 release. The recent Release Candidate of Silverlight 1.0 has many organizations considering whether they should start working with Silverlight. In addition, the Mono project has made tremendous strides in its Moonlight project, which intends to bring Silverlight to the Linux platform. Microsoft is promising to add support for the Opera browser on Windows and Mac. Currently, two operating systems and three browsers are supported. In contrast, the Silverlight plug-in enables an identical development model regardless of user operating system and browser. Usually there are two ways that a development project addresses this: support only a small subset of Web browsers, or increase the number of quality assurance personnel. As a developer creates matrices of browser versions and operating systems, the number of test beds needed becomes enormous. The problem is not simply the necessity for multiple code implementations but also exponentially large testing sets. Silverlight Avoids Cross-Browser/OS Issuesįor most development teams, developing a website that will work identically with the popular browsers of the day (including Internet Explorer, Firefox, Safari and Opera) is a difficult proposition. Sign up for the Development & Architecture Newsletterġ.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |