asp.net 2.0 "plugin" said

asp.net

asp.net 2.0 "plugin" said

Of the new features of ASP.net 2.0, the most "dazzling" is the master page, theme/skin,
Membership and role management, user-defined attributes, and page personalization settings for WebPart.
Except for the first two, the rest are based on the services provided by ***provider.

These provider (classes) are generally defined in the Microsoft Documentation: for ... Provide... Service
It seems to be the same as the general control class, just take it. Actually these provider (class)
Has strongly hinted at Microsoft. NET is a development direction,
This direction is (your website) application "plugin".

"Plug-in" is the old brother for the image of easy to explain the problem borrowed, and not necessarily accurate and rigorous
and the "plugin" concept in the Microsoft documentation is different.

The following youngest brother from the soft, hardware these two angles simply said it as a "plug-in" Reason:

From a hardware perspective: If you imagine a PC, can you think of web.config as a "motherboard"?
And these provider is inserted on the motherboard of the graphics card, sound card, network card .... More abstract some can be considered
These provider are actually equivalent to driver driver. Microsoft has provided us with the Microsoft brand
SqlMembershipProvider, Sqlroleprovider, SqlProfileProvider, SqlPersonalizationProvider
The provider also allows us to reassign them in Web.config to replace them (equivalent to setting up CMOS or "jumper").
This is like no matter what type of brand graphics card (or sound card, network card, etc.) can be plugged into the motherboard as long as it meets the compatibility criteria.

From the software point of view: Since the launch of the Eclips, the development platform of the "plug-in" also with a fire (the browser can already have),
Java programmers are writing "plugins" for a time.
. NET here because there is vs.net so the impact is not very big, but "plug-in" we also use the same.
I wonder if the brothers noticed that VSS is integrated with vs.net in the form of "Plug-ins".
A more pure example is Borland togather for. NET. From these integrations to the IDE's "plugins"
We can see that "plugin" provides a feature extension and upgrades/replacements, and now relies on these provider,
Our own development of the Web site program can also be "plug-ins" of the. For example, if you don't need page personalization
(WebPart) feature, we don't have to "install" the PersonalizationProvider
(In fact, it should be said in turn, what function is required to "install" what provider, but now all are all in advance installed).

So later application development is like the computer market installed, the assembly can be installed?

The answer is yes: When Microsoft showed its VSTS (Visual Studio team System) product, it played a
One line of code does not need to write, to assemble a Web site, and performance/pressure test results are not bad
(Of course, it's not just a "plugin", it's supposed to be called a widget or something).
It's more mad than MDA (a joke)!

The answer is no: In the old brother's opinion, this is ultimately a laboratory product, Microsoft engineers are in the ideal state
Changed a "Magic", on the one hand we do not have a Microsoft engineer so professional, on the other hand, each application has its own special
Business needs, plainly is not necessarily applied on. In addition, Microsoft provides the SQL series provider are based on the 2-tier architecture
Implemented, is difficult to integrate into today's popular multi-tier architecture, for this reason, Microsoft in
Http://msdn.microsoft.com/asp.net/downloads/providers/default.aspx?pull=/library/en-us/dnaspp/html/asp2prvdr01.asp
This provides a sample code download for these provider so that we can disassemble them into multiple implementations.