Frequently asked questions and errors installed under NET! ! !

Author: Multiplayer Source: 9cbs

Q: An error occurred when new projects: Visual Studio .NET has detected that the specified web server is not running is not ASP.NET version 1.1. You will not be able to run an ASP.NET web application or service. Ahttp://support.microsoft.com/default.aspx? Scid = kb; en-us; 817267 --------------------------- -------------------------------------------------- -------------------------------------------------- --Q: About unable to create APS.Web projects AHTTP: //www.9cbs.net/develop/read_article.asp? Id = 19725 ----------------- -------------------------------------------------- -------------------------------------------------- ------------ Q: ASPX project cannot debug a: 1, a debug process has been launched (both projects have opened two projects, and there is a debugged): can only start one; 2. Debug = "false" in the configuration file: change to true; 3, the virtual directory does not establish an application (or empty): "Application" in the virtual directory properties Click Create 4, the project is configured to Release: Point menu "Generated" - configuration, select "Debug" 5, "You don't debug server permissions": Modify IE security settings, "Automatically use the current username and password login" If not, refer to MS solution: Control your error message , You should find a solution in this document http://www.gotdot.com/team/csharp/learn/Whitepapers/howtosolvedebuggerProblems.doc ------------------- -------------------------------------------------- -------------------------------------------------- ---------- Q: Deploy the .NET program to the machine where the .NET FRAMWORK is installed on ahttp://www.microsoft.com/china/techdoc/deploynetApp.mspx- ----------------- -------------------------------------------------- -------------------------------------------------- ----------- Q: When installing VS.NET 2003, there is an error in "Unable to access Windows Installer Components" A: According to the prompt, you should have a problem with Windows Installer. Need to reinstall Windows Installer. Perform the following: First, use MSIEXEC / UnregServer to stop Windows Installer service. Second, download INSTMSIW.EXE, unzip it with WinRAR. Enter the directory. Third, right-click MSI.INF and click Install.

Fourth, install vs.net 2003 ------------------------------------------------------------------------------------------------------------------- -------------------------------------------------- ------------------------------------ Q: VC software package is not available or unregistered A: Symptoms: When a WinForms application is established, the following error message is received: "VC software package is not available or not registered". This error will even appear after it looks at a successful installation. Cause: If the Visual Studio.net installer discovers Some TLB files and DLL files already exist, will not register these files again in the computer, so there is a prompt that "VC software package is not available or unregistered". In most cases, the old version of Visual Studio .NET is easy to cause this error, especially the old version is installed under another operating system. Solution: To solve this problem, you need to run the Visual Studio .NET repair. Since the repair is enforced to register without being registered in some installations The project can be solved more effectively. Follow the steps below: In the Start, point to Settings, click the Control Panel, then click Add / Remove Programs; in the list of installed programs, Click Visual Studio .NET, then click "Change / Remove"; click on the Visual Studio .NET installation dialog 1 2 3 The second item in the project; click "Repair / Replace", follow the screen prompt. More related information : Reproduce this problem to reproduce this problem, preferably two operating systems that are installed on separate partitions. Two Windows XP Professional will reach this. Install Visual Studio .NET under an operating system; The Visual Studio .NET, the installation process is changed during the installation process to match the path to the first installation. The two installation results will be successful. Then start the second installed Visual Studio .NET (you will This problem will be found. This installation form is never recommended, even if the installation option is exactly the same, and you will save disk space, this method has a potential problem. If a Visual Studio .net changes files and registration options, these changes will not be recorded in another Visual Studio .NET, resulting in potential hazards that have unpredictable results. Heads: 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 errors (debug the ASP.NET application in Visual Studio .NET) Common errors in Ahttp: //support.microsoft.com/?id = 306172 ------------------------------- -------------------------------------------------- ---------------------------------- Q: Receive "Unrecoverable Build Error" error message when generating and deploying items (unrecoverable generated error) error message AHTTP: //support.microsoft.com/?i ID =

329214Q: Unable to start debugging on the Web Servera: If you encounter these errors, you need to consider the following questions: Web applications you want to check on the remote server store in Visual SourceSafe and use the FrontPage server to extend web applications Manually attach the content to be checked If you get "unable to start debugging on the web server" error, try check the following: Are you running a Windows version 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 attach it to it manually. (For more information, see Manual Addition and ASP.NET Debug: System Requirements.) Does your web application have a web.config file? Whether the web.config file enables debug mode by setting the debug property to True? For more information, see the debug mode in the ASP.NET application. Does web.config contain any syntax errors? You can check if there is a syntax error by running a web application without debugging. (From the "Debug" menu, select "Start (not debug)".) If there is a syntax error in the web.config, the details are displayed. Are you a member of the debugger user (Debugger users)? If you log in as an administrator, is the administrator in this group? Are you creating a project by specifying a specific IP address (such as 100.20.300.400)? Debug web server requires NTLM authentication. By default, the IP address is assumed to be part of the Internet, and NTLM authentication is not performed on the Internet. To correct this question: When you create an item, specify the name of your computer on the intranet. - or - Add IP address http://100.20.300.400) to the list of trusted sites on your computer. (From Internet Explorer's Tools menu, select "Internet Options" and select the Security tab). Does the computer running the IIS server have installed Visual Studio .NET remote components? Is IIS installed on a local computer (ie computer running Visual Studio .NET) after installation of Visual Studio .NET installed? IIS should be installed before installing Visual Studio .NET. If it is later installed, you may need to fix the .NET framework. Repair the .NET framework into the Visual Studio .NET disc and run : / DotNetFramework / DotNetfx.exe / T: C: / Temp / C :"msiexec.exe / Fvecms C: /Temp/netfx.msi " Does the URL of the project start page correctly? Is the extension and project directory correct? Do IIS security settings correctly? To verify this, check the Default Web Site settings.

Check the IIS Security settings of the Default Web Site From the Start menu, select Programs and Administrative Tools in turn, then click Internet Service Manager (Windows 2000) or "Internet Information Services" (Windows XP ). In the Internet Service Manager or the Internet Information Services dialog box, click Tree Control for your computer. In the Web Site folder, find the Default Web Site. Right click on "Default Web Site" and select Properties. In the Default Web Site Properties window, select the Directory Security tab and click Edit. In the Authentication Method dialog box, select "Anonymous Access" and "Integrated Windows Authentication" (if you haven't selected). Click OK to close the Internet Service Manager or the Internet Information Services dialog. Click OK. For the ATL Server application, verify that the debug predicate is associated with your ISAPI extension. For ASP.NET applications, make sure that the application's virtual folder has an "application name" set in "Internet Service Manager" or "Internet Information Service". Specifying a virtual folder from the Web Application From the Start menu, select Programs and Administrative Tools, and then click Internet Service Manager (Windows 2000) or "Internet Information Services" (Windows XP). In the Internet Service Manager or the Internet Information Services dialog box, click Tree Control for your computer. In the Web Site folder, find this web application. Right click on "Default Web Site" and select Properties. In the Default Web Site Properties window, select the Directory tab. Under Application Settings, click Create. The application name appears in this box. Click "OK" to close the Properties dialog. Click OK to close the Internet Service Manager or the Internet Information Services dialog. Web applications on remote servers If the web application is on the remote server, check the following: Will you run the correct installer to install the ASP.NET/atl Server and Remote Debugger Components on the server? Are you a member of the debugger user (Debugger user "group on the server? Do you have access privileges necessary to debug the process running under the system account? According to the security settings, the ASP.NET application may run under the INetInfo.exe (IIS process), or it is possible to run in the ASP secondary process aspnet_wp.exe. By default, the ASPNET_WP.EXE process runs as a System. To debug applications running under ASPNET_WP.EXE, you need to have administrator privileges or edit the machine.config file for ASPNET_WP.exe so that ASPNET_WP.EXE is running under user accounts. To debug an application running under inetinfo.exe, you must be an administrator on a computer that runs in inetinfo.exe. According to the security settings, the ATL Server application may run under inetinfo.exe or run under the ATL assist process Dllhost.exe. To debug an application running under inetinfo.exe, you must be an administrator on the computer that runs INetInfo.exe, or uses the public language Runtuance Application setting to configure DLLHOST to run as a specific user.

Are you using the Terminal Server try to debug a web application on a remote computer? Under Windows XP, you support the use of "Terminal Server" to remotely debug the native web application. It is not supported in Windows 2000 or Windows NT. WEB applications stored in Visual SourceSafe and extended using FrontPage Server If the web application stores in Visual SourceSafe and uses FrontPage Server Extensions as its web access mode: Visual SourceSafe is located with the FrontPage server / web server On the same computer? If so, you can use "Integrated Authentication" to debug. (To check "Integrated Authentication" settings, see this procedure to check the "default Web site" IIS security settings.) Solving another method of this problem is to change the web access mode from FrontPage to file sharing File Share). Change the web access mode to File Share In the Solution Explorer, right-click the project name, then select Properties from the shortcut menu. In the Properties Page dialog box, open the General Properties folder and select "Web Settings". Under "Web Server Connection", click Web Access Mode and select File Sharing from the list box. Click OK to close the Properties Page dialog. Manual Additional If the corresponding operation is performed in accordance with these troubleshooting steps, the error message is still received when starting debugging, and you may need to try to debug the application by manually attach. Manually attach the launch application without debugging. (From the "Debug" menu, select "Start (not debug)".) Additional IIS processes or auxiliary processes. By default, for the ATL Server application for inetinfo.exe; for the ASP.NET application as ASPNET_WP.EXE. Use the following procedure to determine which process is running under the ASP.NET or ATL Server application. Check which procedure running under the ASP.NET application Using the Visual Studio .NET or other text editor opens the application's Machine.config file. Find the following process model properties: enable If the enable is set to True, the application runs under ASPNET_WP.EXE (this is also the default setting.) If the enable is set to false, the application runs under inetinfo.exe. Check which process of the ATL Server application runs in the Solution Explorer, right-click the project name, and then select "Properties" from the shortcut menu. In the Properties Page dialog box, open the Web Deploy folder and select "General". View Application Protection settings. If this is set to "IIS Process)", the application runs under inetinfo.exe. If this is set to "Medium (Pool)", the application runs under the DLLHost.exe process (same as those in the Pool). If this is set to "High (independent)", the application runs under the DLLHOST.EXE process (different from other ATL Server applications). Click OK to close the Properties Page dialog.