I have been working all day yesterday and I almost broke down! I can't shut down the phone randomly again because of this carelessness. I encountered almost all Net installation and debugging problems. Fortunately, I recorded them one by one. At the same time, I found some related solutions in CSDN, and I dared not enjoy them exclusively for everyone to learn and communicate with each other.
The cause is this: the machine was faked to die when running IE. I was unhappy with it, so I just started it without saying a word, and something happened.
When I reopened the project I was working on, I didn't react for a long time, and the machine became extremely slow. Of course, out of professional sensitivity, I immediately came with Ctrl+Alt+Del. This time it was not good. The CPU occupied 100%, and it was always high. I ran IE but I didn't respond for a long time. My first instinct, was it a hit?
Speed is the best, shut down and restart, immediately open the genuine KV2006 antivirus software, kill it, and after nearly 2 hours of torture, my machine is clean and clean, and there is no shadow of a cancer (absolutely no pornographic films, I am a five-good youth)! Will this happen at first? I called Ctrl+Del+Alt again, check the task manager, see if there are any "alien" invading our territory, and I saw on Baidu that the task manager of Windows is relatively hot, so I went to another aports that is said to be a relatively cool one for process analysis (many articles say that win2000 only has 2 things, and mine came out three), and closed it, the CPU was still 100%, and each process was closed, and the result was the same.-----The first possibility in this way: the possibility of the machine being hit was ruled out!
Since there was no prompt at the beginning, it was just that the CPU was tortured, but it was normal to open vs2003, and it was normal to try to open other projects! Could it be that something went wrong with my program? Without saying a word, I made out yesterday's backup program (this is running normally), renamed the current source file, and put the backup in (I often do this, there was no mistake before), restarted, and opened the project, and the problem remained the same. . . . The second possibility: The possibility of a problem with the program is also ruled out!
Is it just tortured? I posted a post on CSDN, but I couldn't get a good solution. You can't always wait!
Some netizens said that it was because of using an agent to surf the Internet, which caused this problem. I have never used an agent to surf the Internet again! Some netizens also said that it was the CPU resource problems caused by BT and electric donkeys. I denied it without saying a word. I never use BT electric donkeys or the like. What about it? Another netizen posted that I asked me to turn off the SMTP virtual server first and then start it. I tried it according to his method, but it still doesn't work! What about new projects? ? I didn't expect this method at the moment, just create a new project and refer to the original code! A thought flashed through my mind, open, build a new project, KAO, it's over, there's no movement, it's dead. I looked at Ctrl+Alt+Del again, and the CPU was 100% unspeakable, a straight line continued to pass in front of me...
I began to wonder if IIS was causing trouble? ? I found that it was not possible to open the original project under IIS, and the CPU also occupied 100%! Anyway, it was going to die, so it would be useless to do it. I will find out after doing it. So, after restarting the machine, I deleted the virtual directory corresponding to IIS when I was building the original project, and at the same time created a new project with different names. A new problem occurred:
Unable to find script library: /aspnet_client/system-web/v1.14322/
This problem is not difficult and is easy to solve:
The method is:
Click Start → Run: c:\winnt\\framework\v1.14322\aspnet-regiis -c
OK
This problem has been solved, and I think I should name the current project as the original project name. In this way, re-reference the original code should be solved! Say less nonsense, let’s talk about the action----the result! No! It's back to 100% of the original CPU
Depressed, I made myself a little angry! Shut down and restart the 48th time, I turned on VsNet2003 again. In despair, I was dead anyway, and I had to see a way to die even if I die. I opened this project and waited for it to run to see what the final result was! Running like a snail (there is a text prompt like "Opening the web server in the status bar)... After about 30 minutes (I have drunk two cups of tea I made), a dialog box pops up:
Visual Studio cannot create or open the application because this computer does not run a web server. Please start the web server first and then continue with the next step of operation.
This is just a fart, my IIS is obviously open! With the CPU 100% situation, I was patient again, turned on IIS again to check it out, and restarted IIS. At the same time, on another computer, some people said that they wanted to set the access permission of wwwroot folder to everyone, which did not work because my folder was originally shared (of course, it may be different for the problem). The method is:
Permission issues, the user may not have write operations to wwwroot.
Solution: try:
Control Panel--》Management Tools--》Computer Management--》Local Users and Groups
Then add the aspnet user to the administrator group.
After such torture, I simply restarted the machine again to see if there were any new adverse reactions. Hey, it really happened.
New error prompt.
IIS default website home directory; local path settings
Set to "C:\Inetpub\wwwroot". On a local area network, the client can use "http://localhost/Mydir/"Access. To facilitate client access, I've put IIS in silence
The home directory of the website is set to "C:\Inetpub\wwwroot\Mydir". At this time, the client can use "http://localhost/"Access. But, I'm in
2003 When opening this project (MyWeb) in the development environment, the following problem occurs:
The project file cannot be retrieved from the web server. The web project "MyWeb" cannot be opened. File path "C:\Inetpub\wwwroot\Mydir" and URL
“http://localhost/Mydir"Not match. Both need to be mapped to the same server location.
HTTP Error 404: Not Found
There are two more options:
What do you want to do:
1Try again using different folder sharing paths
2. Try to open the project through FrontPage server extension
I think this problem should be a problem on the virtual path. In response to the path prompted by it, I opened IIS and found that the default site path C:\Inetpub\wwwroot\. At the same time, the path of my project is also correct. I accidentally found that the CPU does not account for 100%. It seems that the original problem was solved, but the new problem came out again, but it was not a deal. Let's first CSDN to see if there are similar problems. Fortunately, there are a lot of methods;
Method 1. Enter IIS->Default Website->Right-click "Properties"->Directory Security->Authentication and Access Control->Edit->Change your anonymous login account to Administrator and enter your password
I've tried this, it's useless
Method 2::Reinstall IIS
Open the Windows Component Wizard.
Click Application Server in Components, and then click Details.
In the Application Server dialog box, under Subcomponents of Application Server, click Internet Information Services (IIS), and then click Details.
In the Internet Information Services (IIS) dialog box, under Subcomponents of Internet Information Services (IIS) subcomponents, do any of the following:
To add optional components, select the check box next to the component you want to install.
To delete an optional component, clear the check box next to the component you want to delete.
Click OK until you return to the Windows Component Wizard.
Click Next, and then click Finish.
I'll keep this for the last time
Method 3: Select the "File" menu --> "Open Project on the Web", then find the disk you placed in the project (such as e:\webfile), and then open the project with the extension .vbproj (the same is true for projects with cs). Note: Do not open .sln.
Next, regenerate the solution.
I tried this, but it didn't seem to work, because the new project was not good, and the original one couldn't be opened either.
I solved it with this method
Method 4:
A:1. Open IIS Manager.
2. Right-click on "Default Web Site" and select Properties.
3. Click "Http Header".
4. Click "MIME Types".
5. Click "New".
6. In Extension, enter ".tmp". (No quotes are required)
7. In MIME Type, enter "Temp". (No quotes are required)
Alas, after a long time, I finally got it done! Some of the errors in VS.net2003 made us puzzled. In order to make everyone have some tricks when facing these problems, I searched out some common problems by the way. Fired will help everyone.
Question 1: Cannot create web applications
source:/develop/article/19/
1. When the site home directory does not create an application:
Create WEBAPP through FP extension + virtual directory. The steps are as follows:
(1) Right-click on the site---all tasks--configure server extension
(2) Create a virtual directory *** and make it configure the application
(3) Create a WEB project in VS, with the name also ***
(4) Establish WEB through FP extension
2. Create an application when the site home directory:
The first method - FP extension:
(1) Right-click on the site---all tasks--configure server extension
(2) Create a WEB project in VS, and set the name by yourself
(3) Establish WEB through FP extension
The second method - WEB sharing:
(1) Change the IP address to all unassigned in IIS
(2) Change the address to 127.0.0.1 or LOCALHOST
3. Please try the following method when it cannot be established:
(1) "Site" --- Right click --- "Properties" --- "All tasks" --- "Recalculate hyperlinks on the web"
Then create it through the frontpage server extension
(2) Instructs you to directly access project files on the web server through file sharing; there is no need to install the FrontPage server extension on that server.
When Visual Studio .NET is installed, a "VS Developers" user group is created and the user group is granted read/write permissions to the inetpub\wwwroot folder. Any user who wants to create a web project using a file share on your computer needs to be added to the VS Developers user group. The newly created "VS Developers" group does not have any members, so even users who install Visual Studio must manually add themselves to this group.
If you do not want to install Visual Studio on a server, you can install only server components through the Visual Studio Installer to create a VS Developers group.
(3) Win2003:
In order to test the URL and UNC, a .tmp file is generated under the directory and then a request is made to the file over HTTP. However, in IIS 6, for security reasons, the tmp file is not registered, and by default, it will be blocked and then an HTTP 404 error will be generated.
To solve this problem, please refer to the following method:
1. Open IIS Manager.
2. Right-click on "Default Web Site" and select Properties.
3. Click "Http Header".
4. Click "MIME Types".
5. Click "New".
6. In Extension, enter ".tmp". (No quotes are required)
7. In MIME Type, enter "Temp". (No quotes are required)
There is also a workaround, you can use the following command line:
%systemdrive%\inetpub\adminscripts\ set w3svc/1/root/MimeMap .tmp,temp
When creating a Web Application, you need to create a temporary file with the suffix named .tmp under the creation path.
After creating the project, you will search for project files from the web folder in HTTP, and also seek temporary files. Since IIS in Windows 2003 did not set the .tmp file to MIME type in some installation steps, IIS returned an error of unknown file type, that is, the file cannot be found. So I think your IIS path is not set correctly.
Question 2: Aspx project cannot be debugged
Causes and solutions
1. A debugging process has been started (two projects have been opened at the same time, and one of them is already debugging): only one can be started at the same time;
2. Debug="false" in the configuration file: change to true;
3. The virtual directory has not created an application (or its name is empty): Click "Application" in the virtual directory attribute to create
4. The project is configured as Release: click "Generate" menu - configure, select "debug"
5. "You do not have the permission to debug the server": Modify IE's security settings, "Automatically log in with the current username and password"
Question 3: Automation server cannot create objects
Causes and solutions
1.: Modify the registry ([HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{0D43FE01-F093-11CF-8940-00A0C9054228}\ProgID]
@=""), change FileSystemObject to an arbitrary name
2. Run Regsvr32
Question 4: Cannot start debugging on the web server
Causes and solutions
Does the application have a file? Does the file have a file by setting the debug property to true?
2. Are you a member of the "Debugger Users" group?
Internet Options -> Security -> Intranet -> Custom Level -> User Verification "Automatically log in with current user and password"
Question 5:
The web server reported the following error: "Http/1.1 400 Bad request
Causes and solutions
1. There are two IP addresses. So there is an error in localhost, just change the IP address in iis to "all not allocated".
2. The first step will be to re-register in IIS, run the following command: aspnet_regiis -i
Step 2: Enter the IIS Manager, change "Default Website" - "Properties" - "Website", and change "IP Address" to "(All Not All Allocated)"; click "WEB Service Extension" and change "v1.1.4322" to "Allow".
Question 6: Microsoft Visual Studio .NET 2003 cannot open an existing 1.1 Web project under the following conditions: ? Set 1.1 to "Disable" in the Web Service Extensions list.
- And -
Set 1.0 to Allow in the Web Service Extensions list.
And -
The computer is running Microsoft Windows Server 2003.
When you try to create a new 1.1 project, you may receive the following error message:
Visual Studio .NET has detected that the specified Web server is not running version 1. will be unable to run Web applications or services.
Causes and solutions
Please change the status of 1.1 to "Allow" in the "Web Service Extensions" list in IIS 6.0. To do this, follow these steps: 1. Click Start, point to Programs, and then click Control Panel.
2. Double-click Administrative Tools, and then double-click Internet Information Services (IIS).
3. Click Web Service Extensions.
4. In the Details pane, click v1.1.4322 in the Web Services Extensions list.
5. Click Allow to change the status from "Forbidden" to "Allow".
If your IIS is not 6.0 version. The following methods can be used:
-Start-All Programs-Microsoft Visual Studio .NET2003-Visual Tools-Visual Studio .NET 2003 Command Prompts
After opening the above Cmd command window, enter: aspnet_regiis /i
Question 7: Try to open the web project, the web server reports the following error: http/1.1 500 Internal server error
Causes and solutions
1. Use a proxy to access the Internet
2.regsvr32
3. Step 1: Use the add/remove program first, reinstall the FRONTPAGE extension service in the IIS component.
Step 2: Go to the management tools, INTERNET options, default site, right-click properties. Home directory. Check the write permissions and click Create. OK
4. Run Regsvr32
Question 8:
It has been detected that the specified WEB server is not running ASP.NET version 1.1, and you cannot run WEB applications or services
Causes and solutions:
1. Reason: Delete the "default web site" in IIS, and create a new site by yourself. It runs normally, but it cannot be compiled, and it cannot be created again. There is a non-1.1 version error. The error occurred before because the server used a fixed IP, and the administrator set the IP address in the attribute to the specified IP address.
Solution: 1. Of course, let’s first determine whether the version 1.1 is really installed. Check the path C:\WINNT\\Framework\v1.1.4322, reinstall aspnet_regiis, and make sure that your "Internet Information Service" is using the "default web site" and the IP address in its attribute is "(all not allocated)", rather than the IP address you specified. If IE uses a proxy, check the Bypass Proxy Server for local addresses,
Also: aspnet_regiis parameters
Question 9: http redirect request failed
Reason: Whether to use Forms verification in the program and modify the relevant verification settings in it
Question 10: When developing a new project, it prompts "Cannot establish a connection with the server"
IIS problem
Run C:\WINDOWS\\Framework\v1.1.4322\aspnet_regiis.exe -i
Issue 11: Error while trying to run the project: Unable to start debugging on the web server. Failed to start or Atl Server debugging
Explanation
/?scid=kb;zh-cn;318465
Run in the DOS command window
Enter WINNT\\Framework\v1.1.4322
cd C:\WINNT\\Framework\v1.1.4322
Execute aspnet_regiis.exe /i
Question 12: An error message occurred when creating a new project in VS 2003: VC package is unavailable or not registered
To resolve this issue, you need to run the Visual Studio .NET hotfix. This problem can be solved more effectively because the fix will force registration of some items that are not registered in the installer.
Follow these steps to run the fix:
In the beginning, point to Settings, click Control Panel, and then click Add/Remove Programs; in the list of installed programs listed, click Visual Studio .NET, and then click Change/Remove; click the second item in the Visual Studio .NET Installation Dialog 1 2 3 project;
Click "Repair/Reinstall" and follow the on-screen prompts.
More related information: How to reproduce this problem
To reproduce this problem, it is best to have two operating systems installed on separate partitions, and two Windows XP Professionals will achieve this goal.
1. Install Visual Studio .NET under an operating system;
2. In another operating system, change the default path of the installation during installation to match the path of the first installation. (The results of both installations will be declared successful)
3. Then start the second installation of Visual Studio .NET (you will find the recurrence of this problem).
This installation format is never recommended, even if the two installation options are exactly the same and you will save disk space with this, but the chances of potential problems in this approach are great. If one Visual Studio .NET changes file and registration options, these changes are not recorded in another Visual Studio .NET, causing the potential risk of unpredictable results.
In addition, if you reinstall the system and then reinstall it to the same directory before reinstalling the system (the original files under this directory are not deleted), the error message "VC package is not available or not registered" may also appear!
Issue 13: Error while trying to run the project: Cannot start debugging on the web server
Problem and solutions:
1. Debugging Project
Check if the project has a valid file, whether the file sets "debug" to "true", and whether the debug predicate is associated with .aspx
2. Debug ISAPI applications
Debugging an ISAPI application requires special attention to the setup steps. The general steps of debugging preparation include:
Create solutions for server applications with the option to run services interactively.
Set permissions in User Manager. You must log out and log in again for the permission to take effect.
Stop and restart the service.
3
step1:.Integrated window authentication
Right-click "My Computer"->"Management"->"Services and Applications"->"Internet Information Service Manager"
->"Website"->"Default Website"->"Properties"->"Directory Security" tab->"Authentication and Access Control Block"->"Editor"->Select "Integrated Windows Authentication" (for win2003 systems, other systems are generally the same)
step2. After integrated authentication, use the following windows user account for anonymous users.
The user name is machine name\IUSR_machine name, and the password system will be automatically added. This user belongs to the Guests user group and cannot be changed.
Anonymous access to the built-in account for Internet information services
step3. The logged-in user belongs to the Debuger Group and Administrator group (debug permissions and full control rights to files), and the ASPNET user belongs to the Administrator group (operate apsx file permissions)
step4. In IE, automatically log in with the current username and password (it is necessary to log out and log in again to be valid)
"Tools" -> "Internet Options" -> "Custom Level" -> "Automatically log in with current username and password"
step5. Check whether the "Keep HTTP Connection" check box is selected, and if not, check it.
step6:.No application was created
Control Panel—> Administrative Tools—> Internet Information Services—> Find Your Project
——>Properties——》Virtual Directory Options, there is a <application name> below and a <button> behind,
Check whether to create or delete. If it is created, click it and the button will become deleted and then save.
Under the command prompt of the program's tool, query the parameters aspnet_regiis /all
That's all for the time being, and I hope it will be useful to everyone :)
There are also some related things on MSDN, which I will put for you to see if you encounter problems.
Web Project and Source Code Management Integration in Visual Studio .NET
/library/chs/?url=/library/CHS/sccvs70 ... ntrolintegrationinvisualstudionet_convert.asp
Q: Cannot start debugging, catastrophic error (common errors that occur when debugging applications in Visual Studio .NET)
A:/?id=306172
---------------------------------------------------------------------------------------------------------------------------------
Q: Received "Unrecoverable Build Error" error message when building installation and deploying the project
A:/?id=329214
The cause is this: the machine was faked to die when running IE. I was unhappy with it, so I just started it without saying a word, and something happened.
When I reopened the project I was working on, I didn't react for a long time, and the machine became extremely slow. Of course, out of professional sensitivity, I immediately came with Ctrl+Alt+Del. This time it was not good. The CPU occupied 100%, and it was always high. I ran IE but I didn't respond for a long time. My first instinct, was it a hit?
Speed is the best, shut down and restart, immediately open the genuine KV2006 antivirus software, kill it, and after nearly 2 hours of torture, my machine is clean and clean, and there is no shadow of a cancer (absolutely no pornographic films, I am a five-good youth)! Will this happen at first? I called Ctrl+Del+Alt again, check the task manager, see if there are any "alien" invading our territory, and I saw on Baidu that the task manager of Windows is relatively hot, so I went to another aports that is said to be a relatively cool one for process analysis (many articles say that win2000 only has 2 things, and mine came out three), and closed it, the CPU was still 100%, and each process was closed, and the result was the same.-----The first possibility in this way: the possibility of the machine being hit was ruled out!
Since there was no prompt at the beginning, it was just that the CPU was tortured, but it was normal to open vs2003, and it was normal to try to open other projects! Could it be that something went wrong with my program? Without saying a word, I made out yesterday's backup program (this is running normally), renamed the current source file, and put the backup in (I often do this, there was no mistake before), restarted, and opened the project, and the problem remained the same. . . . The second possibility: The possibility of a problem with the program is also ruled out!
Is it just tortured? I posted a post on CSDN, but I couldn't get a good solution. You can't always wait!
Some netizens said that it was because of using an agent to surf the Internet, which caused this problem. I have never used an agent to surf the Internet again! Some netizens also said that it was the CPU resource problems caused by BT and electric donkeys. I denied it without saying a word. I never use BT electric donkeys or the like. What about it? Another netizen posted that I asked me to turn off the SMTP virtual server first and then start it. I tried it according to his method, but it still doesn't work! What about new projects? ? I didn't expect this method at the moment, just create a new project and refer to the original code! A thought flashed through my mind, open, build a new project, KAO, it's over, there's no movement, it's dead. I looked at Ctrl+Alt+Del again, and the CPU was 100% unspeakable, a straight line continued to pass in front of me...
I began to wonder if IIS was causing trouble? ? I found that it was not possible to open the original project under IIS, and the CPU also occupied 100%! Anyway, it was going to die, so it would be useless to do it. I will find out after doing it. So, after restarting the machine, I deleted the virtual directory corresponding to IIS when I was building the original project, and at the same time created a new project with different names. A new problem occurred:
Unable to find script library: /aspnet_client/system-web/v1.14322/
This problem is not difficult and is easy to solve:
The method is:
Click Start → Run: c:\winnt\\framework\v1.14322\aspnet-regiis -c
OK
This problem has been solved, and I think I should name the current project as the original project name. In this way, re-reference the original code should be solved! Say less nonsense, let’s talk about the action----the result! No! It's back to 100% of the original CPU
Depressed, I made myself a little angry! Shut down and restart the 48th time, I turned on VsNet2003 again. In despair, I was dead anyway, and I had to see a way to die even if I die. I opened this project and waited for it to run to see what the final result was! Running like a snail (there is a text prompt like "Opening the web server in the status bar)... After about 30 minutes (I have drunk two cups of tea I made), a dialog box pops up:
Visual Studio cannot create or open the application because this computer does not run a web server. Please start the web server first and then continue with the next step of operation.
This is just a fart, my IIS is obviously open! With the CPU 100% situation, I was patient again, turned on IIS again to check it out, and restarted IIS. At the same time, on another computer, some people said that they wanted to set the access permission of wwwroot folder to everyone, which did not work because my folder was originally shared (of course, it may be different for the problem). The method is:
Permission issues, the user may not have write operations to wwwroot.
Solution: try:
Control Panel--》Management Tools--》Computer Management--》Local Users and Groups
Then add the aspnet user to the administrator group.
After such torture, I simply restarted the machine again to see if there were any new adverse reactions. Hey, it really happened.
New error prompt.
IIS default website home directory; local path settings
Set to "C:\Inetpub\wwwroot". On a local area network, the client can use "http://localhost/Mydir/"Access. To facilitate client access, I've put IIS in silence
The home directory of the website is set to "C:\Inetpub\wwwroot\Mydir". At this time, the client can use "http://localhost/"Access. But, I'm in
2003 When opening this project (MyWeb) in the development environment, the following problem occurs:
The project file cannot be retrieved from the web server. The web project "MyWeb" cannot be opened. File path "C:\Inetpub\wwwroot\Mydir" and URL
“http://localhost/Mydir"Not match. Both need to be mapped to the same server location.
HTTP Error 404: Not Found
There are two more options:
What do you want to do:
1Try again using different folder sharing paths
2. Try to open the project through FrontPage server extension
I think this problem should be a problem on the virtual path. In response to the path prompted by it, I opened IIS and found that the default site path C:\Inetpub\wwwroot\. At the same time, the path of my project is also correct. I accidentally found that the CPU does not account for 100%. It seems that the original problem was solved, but the new problem came out again, but it was not a deal. Let's first CSDN to see if there are similar problems. Fortunately, there are a lot of methods;
Method 1. Enter IIS->Default Website->Right-click "Properties"->Directory Security->Authentication and Access Control->Edit->Change your anonymous login account to Administrator and enter your password
I've tried this, it's useless
Method 2::Reinstall IIS
Open the Windows Component Wizard.
Click Application Server in Components, and then click Details.
In the Application Server dialog box, under Subcomponents of Application Server, click Internet Information Services (IIS), and then click Details.
In the Internet Information Services (IIS) dialog box, under Subcomponents of Internet Information Services (IIS) subcomponents, do any of the following:
To add optional components, select the check box next to the component you want to install.
To delete an optional component, clear the check box next to the component you want to delete.
Click OK until you return to the Windows Component Wizard.
Click Next, and then click Finish.
I'll keep this for the last time
Method 3: Select the "File" menu --> "Open Project on the Web", then find the disk you placed in the project (such as e:\webfile), and then open the project with the extension .vbproj (the same is true for projects with cs). Note: Do not open .sln.
Next, regenerate the solution.
I tried this, but it didn't seem to work, because the new project was not good, and the original one couldn't be opened either.
I solved it with this method
Method 4:
A:1. Open IIS Manager.
2. Right-click on "Default Web Site" and select Properties.
3. Click "Http Header".
4. Click "MIME Types".
5. Click "New".
6. In Extension, enter ".tmp". (No quotes are required)
7. In MIME Type, enter "Temp". (No quotes are required)
Alas, after a long time, I finally got it done! Some of the errors in VS.net2003 made us puzzled. In order to make everyone have some tricks when facing these problems, I searched out some common problems by the way. Fired will help everyone.
Question 1: Cannot create web applications
source:/develop/article/19/
1. When the site home directory does not create an application:
Create WEBAPP through FP extension + virtual directory. The steps are as follows:
(1) Right-click on the site---all tasks--configure server extension
(2) Create a virtual directory *** and make it configure the application
(3) Create a WEB project in VS, with the name also ***
(4) Establish WEB through FP extension
2. Create an application when the site home directory:
The first method - FP extension:
(1) Right-click on the site---all tasks--configure server extension
(2) Create a WEB project in VS, and set the name by yourself
(3) Establish WEB through FP extension
The second method - WEB sharing:
(1) Change the IP address to all unassigned in IIS
(2) Change the address to 127.0.0.1 or LOCALHOST
3. Please try the following method when it cannot be established:
(1) "Site" --- Right click --- "Properties" --- "All tasks" --- "Recalculate hyperlinks on the web"
Then create it through the frontpage server extension
(2) Instructs you to directly access project files on the web server through file sharing; there is no need to install the FrontPage server extension on that server.
When Visual Studio .NET is installed, a "VS Developers" user group is created and the user group is granted read/write permissions to the inetpub\wwwroot folder. Any user who wants to create a web project using a file share on your computer needs to be added to the VS Developers user group. The newly created "VS Developers" group does not have any members, so even users who install Visual Studio must manually add themselves to this group.
If you do not want to install Visual Studio on a server, you can install only server components through the Visual Studio Installer to create a VS Developers group.
(3) Win2003:
In order to test the URL and UNC, a .tmp file is generated under the directory and then a request is made to the file over HTTP. However, in IIS 6, for security reasons, the tmp file is not registered, and by default, it will be blocked and then an HTTP 404 error will be generated.
To solve this problem, please refer to the following method:
1. Open IIS Manager.
2. Right-click on "Default Web Site" and select Properties.
3. Click "Http Header".
4. Click "MIME Types".
5. Click "New".
6. In Extension, enter ".tmp". (No quotes are required)
7. In MIME Type, enter "Temp". (No quotes are required)
There is also a workaround, you can use the following command line:
%systemdrive%\inetpub\adminscripts\ set w3svc/1/root/MimeMap .tmp,temp
When creating a Web Application, you need to create a temporary file with the suffix named .tmp under the creation path.
After creating the project, you will search for project files from the web folder in HTTP, and also seek temporary files. Since IIS in Windows 2003 did not set the .tmp file to MIME type in some installation steps, IIS returned an error of unknown file type, that is, the file cannot be found. So I think your IIS path is not set correctly.
Question 2: Aspx project cannot be debugged
Causes and solutions
1. A debugging process has been started (two projects have been opened at the same time, and one of them is already debugging): only one can be started at the same time;
2. Debug="false" in the configuration file: change to true;
3. The virtual directory has not created an application (or its name is empty): Click "Application" in the virtual directory attribute to create
4. The project is configured as Release: click "Generate" menu - configure, select "debug"
5. "You do not have the permission to debug the server": Modify IE's security settings, "Automatically log in with the current username and password"
Question 3: Automation server cannot create objects
Causes and solutions
1.: Modify the registry ([HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{0D43FE01-F093-11CF-8940-00A0C9054228}\ProgID]
@=""), change FileSystemObject to an arbitrary name
2. Run Regsvr32
Question 4: Cannot start debugging on the web server
Causes and solutions
Does the application have a file? Does the file have a file by setting the debug property to true?
2. Are you a member of the "Debugger Users" group?
Internet Options -> Security -> Intranet -> Custom Level -> User Verification "Automatically log in with current user and password"
Question 5:
The web server reported the following error: "Http/1.1 400 Bad request
Causes and solutions
1. There are two IP addresses. So there is an error in localhost, just change the IP address in iis to "all not allocated".
2. The first step will be to re-register in IIS, run the following command: aspnet_regiis -i
Step 2: Enter the IIS Manager, change "Default Website" - "Properties" - "Website", and change "IP Address" to "(All Not All Allocated)"; click "WEB Service Extension" and change "v1.1.4322" to "Allow".
Question 6: Microsoft Visual Studio .NET 2003 cannot open an existing 1.1 Web project under the following conditions: ? Set 1.1 to "Disable" in the Web Service Extensions list.
- And -
Set 1.0 to Allow in the Web Service Extensions list.
And -
The computer is running Microsoft Windows Server 2003.
When you try to create a new 1.1 project, you may receive the following error message:
Visual Studio .NET has detected that the specified Web server is not running version 1. will be unable to run Web applications or services.
Causes and solutions
Please change the status of 1.1 to "Allow" in the "Web Service Extensions" list in IIS 6.0. To do this, follow these steps: 1. Click Start, point to Programs, and then click Control Panel.
2. Double-click Administrative Tools, and then double-click Internet Information Services (IIS).
3. Click Web Service Extensions.
4. In the Details pane, click v1.1.4322 in the Web Services Extensions list.
5. Click Allow to change the status from "Forbidden" to "Allow".
If your IIS is not 6.0 version. The following methods can be used:
-Start-All Programs-Microsoft Visual Studio .NET2003-Visual Tools-Visual Studio .NET 2003 Command Prompts
After opening the above Cmd command window, enter: aspnet_regiis /i
Question 7: Try to open the web project, the web server reports the following error: http/1.1 500 Internal server error
Causes and solutions
1. Use a proxy to access the Internet
2.regsvr32
3. Step 1: Use the add/remove program first, reinstall the FRONTPAGE extension service in the IIS component.
Step 2: Go to the management tools, INTERNET options, default site, right-click properties. Home directory. Check the write permissions and click Create. OK
4. Run Regsvr32
Question 8:
It has been detected that the specified WEB server is not running ASP.NET version 1.1, and you cannot run WEB applications or services
Causes and solutions:
1. Reason: Delete the "default web site" in IIS, and create a new site by yourself. It runs normally, but it cannot be compiled, and it cannot be created again. There is a non-1.1 version error. The error occurred before because the server used a fixed IP, and the administrator set the IP address in the attribute to the specified IP address.
Solution: 1. Of course, let’s first determine whether the version 1.1 is really installed. Check the path C:\WINNT\\Framework\v1.1.4322, reinstall aspnet_regiis, and make sure that your "Internet Information Service" is using the "default web site" and the IP address in its attribute is "(all not allocated)", rather than the IP address you specified. If IE uses a proxy, check the Bypass Proxy Server for local addresses,
Also: aspnet_regiis parameters
Question 9: http redirect request failed
Reason: Whether to use Forms verification in the program and modify the relevant verification settings in it
Question 10: When developing a new project, it prompts "Cannot establish a connection with the server"
IIS problem
Run C:\WINDOWS\\Framework\v1.1.4322\aspnet_regiis.exe -i
Issue 11: Error while trying to run the project: Unable to start debugging on the web server. Failed to start or Atl Server debugging
Explanation
/?scid=kb;zh-cn;318465
Run in the DOS command window
Enter WINNT\\Framework\v1.1.4322
cd C:\WINNT\\Framework\v1.1.4322
Execute aspnet_regiis.exe /i
Question 12: An error message occurred when creating a new project in VS 2003: VC package is unavailable or not registered
To resolve this issue, you need to run the Visual Studio .NET hotfix. This problem can be solved more effectively because the fix will force registration of some items that are not registered in the installer.
Follow these steps to run the fix:
In the beginning, point to Settings, click Control Panel, and then click Add/Remove Programs; in the list of installed programs listed, click Visual Studio .NET, and then click Change/Remove; click the second item in the Visual Studio .NET Installation Dialog 1 2 3 project;
Click "Repair/Reinstall" and follow the on-screen prompts.
More related information: How to reproduce this problem
To reproduce this problem, it is best to have two operating systems installed on separate partitions, and two Windows XP Professionals will achieve this goal.
1. Install Visual Studio .NET under an operating system;
2. In another operating system, change the default path of the installation during installation to match the path of the first installation. (The results of both installations will be declared successful)
3. Then start the second installation of Visual Studio .NET (you will find the recurrence of this problem).
This installation format is never recommended, even if the two installation options are exactly the same and you will save disk space with this, but the chances of potential problems in this approach are great. If one Visual Studio .NET changes file and registration options, these changes are not recorded in another Visual Studio .NET, causing the potential risk of unpredictable results.
In addition, if you reinstall the system and then reinstall it to the same directory before reinstalling the system (the original files under this directory are not deleted), the error message "VC package is not available or not registered" may also appear!
Issue 13: Error while trying to run the project: Cannot start debugging on the web server
Problem and solutions:
1. Debugging Project
Check if the project has a valid file, whether the file sets "debug" to "true", and whether the debug predicate is associated with .aspx
2. Debug ISAPI applications
Debugging an ISAPI application requires special attention to the setup steps. The general steps of debugging preparation include:
Create solutions for server applications with the option to run services interactively.
Set permissions in User Manager. You must log out and log in again for the permission to take effect.
Stop and restart the service.
3
step1:.Integrated window authentication
Right-click "My Computer"->"Management"->"Services and Applications"->"Internet Information Service Manager"
->"Website"->"Default Website"->"Properties"->"Directory Security" tab->"Authentication and Access Control Block"->"Editor"->Select "Integrated Windows Authentication" (for win2003 systems, other systems are generally the same)
step2. After integrated authentication, use the following windows user account for anonymous users.
The user name is machine name\IUSR_machine name, and the password system will be automatically added. This user belongs to the Guests user group and cannot be changed.
Anonymous access to the built-in account for Internet information services
step3. The logged-in user belongs to the Debuger Group and Administrator group (debug permissions and full control rights to files), and the ASPNET user belongs to the Administrator group (operate apsx file permissions)
step4. In IE, automatically log in with the current username and password (it is necessary to log out and log in again to be valid)
"Tools" -> "Internet Options" -> "Custom Level" -> "Automatically log in with current username and password"
step5. Check whether the "Keep HTTP Connection" check box is selected, and if not, check it.
step6:.No application was created
Control Panel—> Administrative Tools—> Internet Information Services—> Find Your Project
——>Properties——》Virtual Directory Options, there is a <application name> below and a <button> behind,
Check whether to create or delete. If it is created, click it and the button will become deleted and then save.
Under the command prompt of the program's tool, query the parameters aspnet_regiis /all
That's all for the time being, and I hope it will be useful to everyone :)
There are also some related things on MSDN, which I will put for you to see if you encounter problems.
Web Project and Source Code Management Integration in Visual Studio .NET
/library/chs/?url=/library/CHS/sccvs70 ... ntrolintegrationinvisualstudionet_convert.asp
Q: Cannot start debugging, catastrophic error (common errors that occur when debugging applications in Visual Studio .NET)
A:/?id=306172
---------------------------------------------------------------------------------------------------------------------------------
Q: Received "Unrecoverable Build Error" error message when building installation and deploying the project
A:/?id=329214