Today, we have organized an old project of Visual Studio 2005, which uses the ASP. NET 2.0 Ajax series components. Although it is outdated, some old projects will be maintained in the future.
For the purpose of memo, collect the following information:
Project name |
Installation Package |
ProgramSet |
Namespace |
|
ASP. NET 2.0 Ajax extensions |
Aspajaxextsetup. MSI |
System. Web. Extensions. dllV1.0.61025 |
System. Web. Extensions |
|
ASP. NET 2.0 Ajax future |
Aspajaxctp. MSI |
Microsoft. Web. Preview. dll |
Microsoft. Web. Preview |
|
ASP. NET Ajax Control Toolkit |
The current version of the Ajax Control Toolkit is not compatible with ASP. NET 2.0. The latest version that is compatible with ASP. NET 2.0 can be found here: 20229 Ajaxcontroltoolkit.zip Contains all space,Test Framework, sample Website and VSI |
Ajaxcontroltoolkit. dll |
Ajaxcontroltoolkit |
|
It is rare to see that the naming of the assembly/namespace is so messy in the. NET component provided by Microsoft. In most cases, the organization of the. NET namespace is rigorous and satisfactory.
However, it is not because the three projects have different development forms/maintenance organizations that make naming messy.
It would be nice to start a negotiation. Otherwise, the price would be this afternoon, for example, Microsoft. web. preview. the DLL function makes me look like a clue to the case. I searched twice to know that it was the "ure" Of The Year. Fu should be fu, And I should change the "preview" when it is my turn to name the assembly "! Painful!