After learning ASP. NET 2.0 for a while, I had some thoughts.

I started learning from. Net beta2 and officially used. net1.1 for development. That is to say ,. when net1.0 came out, the vast majority of people were in the learning stage. The reason is, of course, many people did not decide whether to study. net, and. net is indeed more difficult than the previous Delphi and VB6, and. net1.0 was just launched. In consideration of stability and functionality, I think most people are using it. NET 1.0 is used as a learning tool, and vs.net 2002 is used as a trainer who is familiar with Microsoft's next-generation development environment.

However. NET 1.1 is different, and more people begin to learn. net, many people come from the Java side, after all. net configuration is much simpler than Java, and enough Chinese documents also reduce the threshold for entry. Of course, as you learn more, some important components can be used.CodeIt also increases, such as FTP, mail, compression and decompression, various controls, and solutions for specific work written with full effort. Of course, most of these software runs under. net1.1.

Now, Microsoft has launched. NET 2.0 beta1. Since it has been released, it will not be too far away from the official version. Of course, when the official version of. NET 2.0 SDK is released, there will certainly be a Chinese SDK. It certainly solved the existing problems in. NET 1.1 and added many features.
For example, the vs2003 web project debugging problem that many people have scratched their heads, and the use of response. Redirect () after session/cookie operations are not reflected.

In this way ,. NET 2.0 (I focus on ASP.net 2.0) and. NET 1.1 has very low compatibility. I have discovered that creating custom web server controls within 1.1 prevents multiple identical controls from registering client scripts

System. Web. UI. Page. isclientscriptblockregistered ()
System. Web. UI. Page. isstartupscriptregistered ()
System. Web. UI. Page. registerclientscriptblock ()
System. Web. UI. Page. registerrequirespostback ()

These four methods have been declared as obsolete methods by the feature system. obsoleteattribute. That is to say, in Asp.net 2.0, you cannot use the script registration method of any client. It seems that you can only use response. Write () for manual writing. That is to say, there is no way to re-compile the code written in 1.1 Under 2.0 and it will become a 2.0 component.

Well, I 've mentioned a lot above, but it shows that. NET 1.1 has little compatibility with. NET 2.0. However, the. NET Runtime Library has the advantage of coexistence of execution. REFERENCEProgramIs this Assembly running under the CLR Control of. NET 1.1 or under. NET 2.0?

If the 1.1 assembly is executed in the 1.1 CLR. Many of the components I have written, many down components, basically run in the 1.1 environment. If I use 2.0, these components cannot be discarded. So can class calls and parameter passing through these components work properly? Especially for parameters. It is okay to pass the basic types such as string and int. But if the parameter is a self-written class, the class instance written in 1.1 is returned to the Code in 2.0 as the return value, can this work? I'm skeptical.