Shulou(Shulou.com)06/02 Report--

Today, I will talk to you about what is the solution that VS2003 can not start debugging. Many people may not know much about it. In order to make you understand better, the editor has summarized the following for you. I hope you can get something according to this article.

Although many people have studied that VS2003 can't start debugging, its security is also improving year after year. It is entirely possible to prevent VS2003 from starting debugging, but only if you have a deep understanding of what VS2003 is and how it works.

At first, I thought it was an old problem again, but I adjusted it according to the old way. Right-click the website in the IIS manager, → properties, → directory security, → authentication, → "integrated authentication". After the change, I found that it still failed. Try other methods, add permissions and modify the expansion of FrontPage services, the common methods mentioned on the Internet have been tried all over and can't be done. It is found that at compile time, there is a sentence in the output column of VS that the process "[3664] w3wp.exe" automatically attached to the computer "9LD9TY0AKKIETZX" failed. The error code is 0x8013134b. So check again, found the root cause of the disease, originally because my machine is not only installed with VS2003 but also installed with VS2005, and IIS uses the ASP.NET2.0 version by default, so just go to IIS- > website-> right-click Properties-> ASP.NET- > drop-down list box to select the version as above 1.1 on OK.

So I went to IIS to change it. Only to find that there is only one ASP.NET v2.0.50727 in me, and even there is only one ASP.NET v2.0.50727 Web service extension in the Web service extension. Fortunately, the blind cat ran into a dead mouse, tried to find the Microsoft Visual Studio .NET 2003-> Visual Studio .NET tools-> Visual Studio .NET 2003 command prompt in the start menu, ran "aspnet_regiis / I" in the open window, re-registered it, and then went to the Web service extension in IIS to see that in addition to the original ASP.NET v2.0.50727, there was finally another ASP.NET v1.14322 that was set to allow.

Then adjust the ASP.NET option in the properties of the website, and find that there is already an ASP.NET version: 1.1.4322. Select the post-point to determine and then run the compilation, OK, and it is done.

For the example program of C++NPv1, there are one or two words that have to be said, the runtime prompt message is too bad! The connection of the client, the message sending and the receiving link of the server, and there was no hint to receive the message, which made me think that the program was not running properly. I added a line of cout in the client LOGGING_CLIENT.CPP.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.