In the last installment we introduced the basic concepts behind the Microsoft Managed Extensibility Framework and built a very simple example, expending a ton of effort for very little return. In this installment, we’ll actually utilize the framework to build an application demonstrating pluggable components in use.
Most developers at one time or another have found it necessary to componentize their application to allow new pieces to be “plugged in” without rebuilding the application. While there are existing frameworks which address this area, such as one of the many Dependency Injection frameworks, they tend to be much broader in scope, and therefore more complicated to use.
Have you ever had to take over a project, fix a bug, or code a feature? How often have you felt uncertain, lost, or upset? How many times have you wanted to find the guy who wrote the piece of code you’re working on and … thank him warmly? See figure 1. If you’re living in the same world as we are, it’s happened to you at least few times.
It’s nice that we can create changes in Groovy objects that can be observed by an interested party, but that is only half the story. Really, we want to do some cool stuff with these changes, and what would be really magical is if we could do some of these things automatically.
Exception safety is an essential aspect of good C++ code, and code that uses concurrency is no exception. In fact, parallel algorithms often need more care taken with regards to concurrency than normal sequential algorithms.
Regular e-commerce shopping carts work fine if the functionality of the store site is limited to listing products, allowing customers to purchase them, accepting credit card payments, and all of the other e-commerce features offered by these shopping cart solutions. But what if you also want to support collaborative editing of content, community forums, and other capabilities that could help increase traffic to your site, but are usually only found in content management systems (CMSs)?
As part of the Information Revolution that is changing the way that the world works and plays, people are increasingly turning to the Internet for the information they use to make decisions — financial, professional, health, etc. Consequently, news publications that are printed and mailed through the post are being supplanted by portal news sites, blogs, and online newsletters (oftentimes referred to as “e-zines” — electronic magazines).
Even though it is possible to do Web development and testing on a remote server, it is better to fully develop a new Web site on a local Web server, and then upload everything when it is finished, for many reasons: 1) Keeping the unfinished site off the Internet is safer, because as you begin developing the site, you probably have not put in all of your code for neutralizing any potential attacks against your site, including cross-site scripting (XSS) vulnerabilities…
Apr 15, 2008 - 96 Comments
Aug 6, 2008 - 20 Comments
Mar 7, 2008 - 13 Comments
Oct 8, 2010 - 2 Comments
Sep 22, 2010 - 0 Comment
Aug 30, 2010 - 1 Comment