Summary of Common Errors and solutions for ASP. NET compilation and execution

21. vs2005 cannot switch from source file mode to view mode

Solution: Run devenv/resetskippkgs (WIN + R cmd) in DOS)

22. Validation of viewstate Mac failed

Solution: Add enableviewstate = "false" enableviewstatemac = "false" to the top page of the page to solve this problem.

23. Automation server can't create object "(The Automation server cannot be created)

Solution: Run regsvr32 scrrun. dll.

24. Package loading failed

The package "Visual Web Developer Trident designer package" (guid =

{30ae7e28-6c02-496d-8e43-85f7a90aeff1 }.

Solution:

1. Set the system variable vslogactivity = 1

2. Create the activitylog. xml file in the % appdata % \ Microsoft \ visualstudio \ 8.0 \ folder.

Error

Microsoft Visual Studio

Loadlibrary failed for package [Visual Web Developer Trident designer package]

{30ae7e2b-6c02-496d-8e43-85f7a90aeff1}

--------------------------------------------------------------------------------

8007007e

C: \ Program Files \ Microsoft Visual Studio 8 \ common7 \ packages \ tridsn. dll

3. Copy the gdiplus. dll file from winnt \ microsoft. Net \ framework \ v2.0.xxx to the Program Files \ Visual Studio 8 \ common7 \ packages folder.

4. Run devenv/resetskippkgs on the command line.

25. Error spawning 'cmd.exe '.

Solution: Copy cmd.exe to the VC/bin directory under the vs installation directory to solve the problem.

26. Try to read or write the protected memory

Solution: hardware problems and general memory problems

27. Unable to find the list signature certificate in the certificate store

Solution: use NotePad to open the. csproj file of the project and delete a file similar

28. The target "resolvekeysource" does not exist in the project ".

Cause: this problem is rare. After querying the relevant foreign materials, it is generally said that the deployment is not a standard solution, and the following things need to be restored in the command prompt provided by

Solution:

(1 ).CodeSave as an XML file and name it testbuild. xml

<Project defaulttargets = "build" xmlns = "http://schemas.microsoft.com/developer/msbuild/2003">

<Propertygroup>

<Targetconnectionstring> Data Source =. \ sql2005 % 3 Buser id = sqluser % 3 bpooling = false % 3 bpassword = x </targetconnectionstring>

</Propertygroup>

<Itemgroup>

<Databaseproject include = "database1 \ database1.dbproj"/>

<Databaseproject include = "database2 \ database2.dbproj"/>

</Itemgroup>

<Target name = "buildalldatabaseprojects">

<Msbuild

Properties = "targetconnectionstring = $ (targetconnectionstring )"

Projects = "@ (databaseproject )"

Targets = "build; deploy">

</Msbuild>

</Target>

(2) Run msbuild/T: buildalldatabaseprojects testbuild. XML in the command prompt.

</Project>

29. The null value cannot be inserted into the column '**'

Cause: This is a database table design error. The attribute that cannot be null is set in the fields of the involved table, but the input value is null. Therefore, an error is returned.

Solution: Check whether the passed value is null, or modify the attribute of the column corresponding to the table in the database.

30. Failed to load type "namespace. Class "...

Cause:

(1) The project is not compiled after modification.

(2) The original namespace in the project may have been modified.

(3) The ascx or other pages required by the project do not exist or are not included in the project

Solution:

(1) After the modification is completed, re-generate or compile the entire project or solution.

(2) manually modify the changed namespace. Pay attention to the Case sensitivity of the name and re-compile it.

(3) include relevant files in the project