The reason for encountering this anomaly is accidental:
Phenomenon:
Solution in the process of rebuild power outage, call recovery, re-compile the entire solution not error, but in the browsing page is always not normal browsing, and in the Design view, each ASPX's first line of code is an error.
Resolution process:
Search to find a lot of domestic programs, some suggestions to re-reference AjaxControlToolkit.dll, there is to clear ASP. NET cache files, but did not see the desired effect, finally in a foreign MSDN post (HTTP/ SOCIAL.MSDN.MICROSOFT.COM/FORUMS/EN-US/CSHARPIDE/THREAD/352C58EC-65D8-4D77-AC7B-D2338C621EF3) See a variety of approaches.
The relevant method can try, not guarantee that all the solutions can achieve the effect, but should also sorta it. Oh.
Scenario 1: Empty the Temporary ASP. Net Files folder, recompile
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP. Files\mywebservice and recompiled and it worked fine.
This method is the most recommended program on the Internet, it seems to be feasible and not feasible. Some of these files cannot be deleted directly, and they need to be removed by special means.
Scenario 2: Uninstall all the net Framework versions on the system, IIS, reinstall Net Framework,iis
This method seems to be troublesome, and it is not quite certain that the effect of solving the anomaly can be achieved. As far as the online results are concerned, the majority of people doing so do not solve the problem. Note The order of installation here
Uninstall. NET (runtime and SDK)->uninstall Iis->install. NET (runtime and SDK)->install IIS
Scenario 3: This method I do not understand, it does not explain, seemingly more complex background:the assembly causing me trouble was built in house and I do not have the source code .
Required:you need the Visual Studio SDK for Ildasm.exe
Steps:
1.) disassemble the. dll with the command Ildasm.exe assemblyname.dll/out:assemblyname.il
2.) Open the newly created assemblyname.il with a text editor and search for "PermissionSet"
3.) Find and delete the following lines:
. PermissionSet Reqmin
= {[Mscorlib]system.security.permissions.permissionsetattribute = {property string ' Name ' = string (' Nobody ')},
[mscorlib] System.Security.Permissions.SecurityPermissionAttribute = {property bool ' execution ' = bool (TRUE)}}
4.) Save and rebuild the assembly with the following Command:ilasm.exe Assemblyname.il/dll
5.) Throw The new DLL in your bin directory or if it's strong named and needed in the GAC can put it there.
Scenario 4: Clear the system disk: \ user \ user name \appdata\local\temp\temporary ASP.
C:\Users\\AppData\Local\Temp\Temporary ASP. NET Files
I took care of this scheme (which is usually solved with this), which happens to be my win7 system. But it seems that this is better with the scheme 1. Note: The vista system and the WINDOW7 system are especially suitable for
A little experience to share with you. Please correct me.
Transferred from: http://www.dezai.cn/blog/article.asp?id=355
Exception: Handling of hresult:0x80070057 (E_INVALIDARG)