Finally, I figured out why the ASP. NET option in IIS cannot be found in Framework 3.5?

I am studying vs2008 and found that Framework 3.5 is included in vs2008. So I went to IIS ASP. NET to check if there is any option.
No. As a result, the script does not have a ing. If you registered the framework region, you cannot find aspnet_regiis.exe.
I registered v3.5and found that the domain name is vfservers.exe, which is similar to that of vfservers.exe.
I see add and delete Program There is Framework 3.5 in it. Why cannot script ing be implemented? I have never understood why
No? According to common sense: vs2003 with framework1.1, vs2005 with framework2.0, vs2008 last time you held a press conference in vs2008 (Microsoft 18
Layer) I said that it does not contain framework3.0, 3.0 contains WCF, this time should always be framework3.5, right? Confused. I believe many people believe that
Just as confused.
Finally, some people (volnet (I can call it big V) answered the question in Lao Zhao's blog. Thank you very much.
Q: Why is the ASP. NET option in IIS not found in Framework 3.5?
A: 3.0 3.5 contains additional functions, but their compiled Code Or 2.0, which is similarArticle There are lambda and past
The target code compiled using the delegate method is based on 2.0, because the. NET Framework is based on static compiled code, so 2.0
This explains Il.
Other answers:
After studying. Net 3.5 over the past few days, I found a question: Why can't I see ASP. NET 3.5 in IIS? In the past, the execution file of aspnet_regiis.exe was not found in. NET 2.0 !!
Later, I realized that ASP. NET 3.5 only uses the. NET Framework 3.5 component (assembly! The entire core architecture is still built. NET 2.0 ,.. net 3.5 many assemblies have been re-written, and the execution speed is also higher. NET 2.0 components are still fast.
If you use Visual Studio 2008 to open a website, you can open web. config and you will find that a bunch of Assembly definitions appear in the <assemblies> section, whose versions are 3.5.0.0.
<Compilation DEBUG = "true">
<Assemblies>
<Add Assembly = "system. Core, version = 3.5.0.0, culture = neutral, publickeytoken = b77a5c561934e089"/>
<Add Assembly = "system. Data. datasetextensions, version = 3.5.0.0, culture = neutral, publickeytoken = b77a5c561934e089"/>
<Add Assembly = "system. Web. Extensions, version = 3.5.0.0, culture = neutral, publickeytoken = 31bf3856ad364e35"/>
<Add Assembly = "system. xml. LINQ, version = 3.5.0.0, culture = neutral, publickeytoken = b77a5c561934e089"/>
</Assemblies>
</Compilation>
So ASP. net 3.5 programs to be installed on IIS do not need to specify ASP.. Net version 3.5, continue to use ASP. NET 2.0, but the operating system must be installed first. net Framework 3.5 runtime!