Net installation, debugging common problems and errors!!!

Author: Many people

Source: Csdn

Q: Error creating new project: Visual Studio. NET has detected that the specified Web server is not running ASP.net version 1.1. You will not be able to run the ASP.net Web application or service. ahttp://support.microsoft.com/default.aspx?scid=kb;en-us;817267 --------------------------------------------------------------------------------------------------------------- ------------------ Q: Solutions to the inability to create a aps.web project ahttp://www.csdn.net/develop/read_article.asp?id=19725 --------------------------------------------------------------------------------------------------------------- ------------------ Q:aspx Project cannot be debugged A:1, a debugging process has been started (two projects have been opened and one is already being debugged): Only one can be started at the same time; 2, in the configuration file debug= "false": change to true; 3, the virtual directory does not establish an application (or empty name): In the Virtual directory Properties "Application" click to create 4, project configuration for release: Point Menu "Build"-Configuration, select "Debug" 5, "You do not debug the server permissions": Modify the security settings of IE, "automatically use the current username and password login" If not, refer to the solution for MS: In contrast to your error message, you should find a solution in this document Http://www.gotdotnet.com/team/csharp/learn/whitepapers/howtosolvedebuggerproblems.doc --------------------------------------------------------------------------------------------------------------- ------------------ Q: Deploy the. NET program to a machine that does not have the. NET Framwork installed Ahttp://www.microsoft.com/china/community/program/originalarticles/techdoc/deploynetapp.mspx --------------------------------------------------------------------------------------------------------------- ------------------ Q: When installing Vs.net 2003, you encounter an "inaccessible Windows Installer component" error A: According to the prompts, there should be a problem with Windows Installer. You need to reinstall Windows Installer. Perform the following actions: First, use Msiexec/unregserver to stop Windows Installer service. Second, download InstMsiW.exe, with winrar decompression open. Enter the directory. Third, right click Msi.inf, click Install. Iv. Installation of Vs.net 2003 --------------------------------------------------------------------------------------------------------------- ------------------ Q:VC package is not available or not registered A: Symptoms: When you set up an WinForms application, you receive the following error message: "The VC package is not available or not registered." This error may even appear after a successful installation appears. Cause: If the Visual Studio.NET installer discovers that some TLB files and DLL files already exist, the files will not be registered with the computer again, so It is possible that the "VC package is not available or unregistered" prompts. In most cases, the old version of Visual Studio. NET can easily cause this error, especially if the old version is installed under another operating system. Solution: To work around this problem, you need to run visual Studio. NET hotfix. This problem can be resolved more effectively because the hotfix enforces registration of items that are not registered in the installer. Follow these steps to run the hotfix: In the beginning, point to Settings, click Control Panel, and then click Add/Remove Programs. In the list of listed installed programs, click Visual Studio. NET, and then click Change/Remove; Click Visual Studio. NET Installation dialog box 1 2 3 items in the second item; Click "Repair/Reload" and follow the on-screen instructions. More information: The practice of reproducing this problem To reproduce this problem, it is best to have two operating systems installed on separate partitions. Two Windows XP Professional will do this. Install Visual Studio. NET under one operating system; Under another operating system, visual Studio. NET, which changes the installation's default path during the installation process to match the path of the first installation. Two installation results will be successful. Then start the second installation of Visual Studio. NET (You'll find that the problem recurs). This form of installation is never recommended, even if the two installation options are identical, and you will save disk space, but this approach has a great chance of potential problems. If a visual Studio. NET changes the file and registration options, and these changes are not recorded in another visual Studio. NET, resulting in the potential danger of unpredictable results. Citation: http://zhuonline.51.net/blogs/archives/000045.html http://support.microsoft.com/default.aspx?scid=http:// Support.microsoft.com:80/support/kb/articles/q320/4/27.asp&nowebcontent=1 --------------------------------------------------------------------------------------------------------------- ------------------ Q: Cannot start debugging, catastrophic error (common errors that occur when debugging ASP.net applications in Visual Studio. NET) ahttp://support.microsoft.com/?id=306172 --------------------------------------------------------------------------------------------------------------- ------------------ Q: Receive "Unrecoverable build Error" (Unrecoverable generation Errors) error message when building installation and deployment projects ahttp://support.microsoft.com/?id=329214 Q:unable to start debugging on the Web server A: If you encounter these errors, you need to consider the following issues: What to check WEB applications on a remote server Web applications stored in Visual SourceSafe and using the FrontPage server Extensions Manually Attach What to check If you get the "Unable to start debugging on the WEB server" error, try checking the following: Whether you are running a version of Windows that allows the Visual Studio debugger to automatically attach to a WEB application. If not, you need to start the application without debugging, and then manually attach to it. (For more information, see Manual Attach and asp.net debugging: System requirements.) ） Whether your WEB application has a Web.config file. Whether the Web.config file enabled debug mode by setting the Debug property to True. For more information, see Debug mode in asp.net applications. Whether the web.config contains any syntax errors. You can check for syntax errors by running the Web application without debugging. (from the Debug menu, choose Start (without Debugging). If there is a syntax error in web.config, the details are displayed. Whether you are a member of the Debugger Users group. If you are logged on as an administrator, the administrator is in the group. Whether you created the project by specifying a specific IP address (such as 100.20.300.400). Debugging a WEB server requires NTLM authentication. By default, IP addresses are assumed to be part of the internet and are not NTLM authenticated on the Internet. To correct this problem: When you create a project, you specify the name of the computer on the Intranet. Or Add the IP address http://100.20.300.400 to the list of trusted sites on your computer. (from the Internet Explorer Tools menu, select Internet Options, and then select the Security tab). Whether the computer running the IIS server has the Visual Studio. NET remote component installed. Whether IIS is installed on the local computer (that is, the computer that is running Visual Studio. NET) after Visual Studio. NET is installed. IIS should be installed before Visual Studio. NET is installed. If it was later installed, you may need to fix the. NET Framework. Fix the. NET Framework Insert the Visual Studio. NET CD and run <dvd drive>:/wcu/dotnetframework/dotnetfx.exe/t:c:/temp/c: "Msiexec.exe/fvecms c:/temp/netfx.msi" Or Insert the Visual Studio. NET Windows Components Update CD and run &LT;CD drive>:/dotnetframework/dotnetfx.exe/t:c:/temp/c: "Msiexec.exe/fvecms c:/temp/netfx.msi" Whether the URL of the project start page is specified correctly. The extension and project directory are correct. Whether IIS security settings are set correctly. To verify this, check the default Web site settings. Check the IIS security settings for the default Web site From the Start menu, select Programs and Administrative Tools, and then click Internet Services Manager (Windows 2000) or Internet Information Services (Windows XP). In the Internet Service Manager or Internet Information Services dialog box, click the tree control for your computer. In the Web Sites folder, locate the default Web site. Right-click the default Web site and select Properties. In the default Web Site Properties window, select the Directory Security tab and click Edit. In the Authentication Methods dialog box, select Anonymous access and integrated Windows authentication, if not already selected. Click OK to close the Internet Services Manager or Internet Information Services dialog box. Click OK. For an ATL Server application, verify that the DEBUG verb is associated with your ISAPI extension. For ASP.net applications, make sure that the application's virtual folder has the application name set in Internet Service Manager or Internet Information Services. To specify a virtual folder for a WEB application From the Start menu, select Programs and Administrative Tools, and then click Internet Services Manager (Windows 2000) or Internet Information Services (Windows XP). In the Internet Service Manager or Internet Information Services dialog box, click the tree control for your computer. In the Web Sites folder, locate the Web application. Right-click the default Web site and select Properties. In the default Web Site Properties window, select the Contents tab. Under Application settings, click Create. The application name appears in this box. Click OK to close the Properties dialog box. Click OK to close the Internet Services Manager or Internet Information Services dialog box. WEB applications on a remote server If the Web application is located on a remote server, check the following issues: Whether the correct setup program is running to install the Asp.net/atl server and remote debugger components on the server. Whether you are a member of the Debugger Users group on the server. Whether you have the necessary access privileges to debug a process running under the system account. Depending on the security settings, the ASP.net application may run under the Inetinfo.exe (IIS process), or it may run under the ASP worker process aspnet_wp.exe. By default, the Aspnet_wp.exe process runs as SYSTEM. To debug an application running under aspnet_wp.exe, you need administrator privileges or edit machine.config files for aspnet_wp.exe so that aspnet_wp.exe runs under a user account. To debug an application running under Inetinfo.exe, you must be an administrator on the computer that is running inetinfo.exe. Depending on the security settings, the ATL Server application may run under Inetinfo.exe or it may run under the ATL worker process Dllhost.exe. To debug an application running under Inetinfo.exe, you must be an administrator on the computer that is running inetinfo.exe, or configure Dllhost to run as a specific user using the common language runtime application settings. Are you using Terminal Server to try to debug a WEB application on a remote computer. Under Windows XP, remote debugging of native WEB applications is supported by using Terminal Server. It is not supported under Windows 2000 or Windows NT. Web applications stored in Visual SourceSafe and using the FrontPage server Extensions If the Web application is stored in Visual SourceSafe and uses the FrontPage Server extensions as its Web Access mode, check the following questions: Whether Visual SourceSafe is on the same computer as the FrontPage server/web server. If it is, you can use integrated authentication for debugging. (To check the integrated authentication settings, see this procedure to check the IIS security settings for the previous default Web site.) ） Another way to resolve this problem is to change the Web access mode from FrontPage to File Share (Share). Change Web access mode to File Share (Share) In Solution Explorer, right-click the project name and choose Properties from the shortcut menu. In the <Project> Property Pages dialog box, open the Common Properties folder, and then select Web Settings. Under Web server connections, click Web Access mode, and then select File Sharing from the list box. Click OK to close the <Project> Property Pages dialog box. Manually Attach If you follow these troubleshooting steps and you still receive an error message when you start debugging, you may want to try to debug your application by attaching manually. Manually Attach Start the application without debugging. (from the Debug menu, choose Start (without Debugging). ） Attach to the appropriate IIS process or worker process. By default, the ATL Server application is inetinfo.exe, and the ASP.net application is aspnet_wp.exe. Use the following procedure to determine which process the ASP.net or ATL Server application runs under. Check which process the ASP.net application runs under Open the application's Machine.config file using Visual Studio. NET or another text editor. Locate the following process Model properties: Enable If enable is set to TRUE, the application runs under aspnet_wp.exe (this is also the default setting.) ） If enable is set to FALSE, the application runs under Inetinfo.exe. Check which process the ATL Server application runs under In Solution Explorer, right-click the project name and choose Properties from the shortcut menu. In the <Project> Property Pages dialog box, open the Web deployment folder, and then select General. View the application protection settings. If this setting is low (IIS process), the application runs under Inetinfo.exe. If this setting is Medium (pool), the application runs under the Dllhost.exe process (the same as an ATL Server application that is placed in a pool). If this setting is high (standalone), the application runs under the Dllhost.exe process (unlike other ATL Server applications). Click OK to close the <Project> Property Pages dialog box. Please see debugging scripts and the Web: errors and troubleshooting Q:web Access failed The default Web Access mode for this project is set to file share, but cannot be http://localhost/bweb from the path "D:/inetpub/bweb" Project folder, the error returned is: The Web project "bweb" could not be opened. The file path "D:/inetpub/bweb" does not match urlhttp://localhost/bweb. The two need to reflect Shoot to a different server location. HTTP Error 404:not Found A:1. Open IIS Manager. 2. Right-click "Default Web Site" and select Properties. 3. Click "Http Header". 4. Click "MIME Types". 5. Click "New". 6. In extension, enter ". tmp". (No quotes required) 7. In the MIME type, enter "Temp". (No quotes required) Q:vs. NET Debugging issues A: About VisualStudio.NET debugging a series of problems, such as no permissions to debug the Web server, not belong to the Debugger Users group, can not debug, and so on, in the VS7 Debugger doesn ' t work. What can I dohttp://blogs.msdn.com/mkpark/articles/86872.aspx) The paper finds the answer. I've had a situation where I have no permissions to debug on a Web server, and then the Internet options for IE are selected-> security->intranet-> Custom Level-> user-authenticated "automatically log on with current user and password" to resolve problems that cannot be debugged. How can you think vs.net can't debug and change IE options