www root problem
-
Just googled for that error, and there is pretty much info out there. Start here for example: http://support.microsoft.com/default.aspx?scid=kb;EN-US;306172[^]
hi, i've tried everything n it sill won't work.. see, my friend and I are doing this project. we send the proj to each other every now and then for modification. everything was fine until 2 days ago. my friend's visual studio happens to be working fine with this proj but mine doesn't. i kept getting those error.. even wen i created a new asp.net proj in vs.net AND send it ova to my frien, it works ova there. but wen he send me back the same file i've sent him, i can't open it in my com.. the thing is it happens to me and most of my other frien.. but not my proj partner. my proj partner keeps his com with the latest windows update. cud it be IIS prob? but we both using version 5.1.. n my frien didnt have any windows update 2 days ago. why?????????? or cud it be cause of .net framework service pack1? Chris
-
Hi guys i have a problem of running my friends program after he send mi the file below is the two error i have encounter (start without debugging) Access denied to 'c:\inetpub\wwwroot\WebApplication1\'. Failed to start monitoring file changes. (F5) Error while trying to run project: Unable to start debugging on the web server. server side-error occurred on sending debug HTTP request
There are actually many reasons. MSDN it up. The most common I may say is when the path specified in the solution file .sln doesn't match. Edit the following entry in the solution file to match your directory structure. Project("{Some Hex Key}") = "SolutionName", "http://localhost/SolutionName/SolutionName.csproj PS: Solution Name is the the name of your solution. ---------- user9 A student knows little about a lot. A professor knows a lot about little. I know everything about nothing.
-
hi, i've tried everything n it sill won't work.. see, my friend and I are doing this project. we send the proj to each other every now and then for modification. everything was fine until 2 days ago. my friend's visual studio happens to be working fine with this proj but mine doesn't. i kept getting those error.. even wen i created a new asp.net proj in vs.net AND send it ova to my frien, it works ova there. but wen he send me back the same file i've sent him, i can't open it in my com.. the thing is it happens to me and most of my other frien.. but not my proj partner. my proj partner keeps his com with the latest windows update. cud it be IIS prob? but we both using version 5.1.. n my frien didnt have any windows update 2 days ago. why?????????? or cud it be cause of .net framework service pack1? Chris
-
no. ok to be sure, how would i check if i've install it? Chris
-
no. ok to be sure, how would i check if i've install it? Chris
-
hi, i've tried everything n it sill won't work.. see, my friend and I are doing this project. we send the proj to each other every now and then for modification. everything was fine until 2 days ago. my friend's visual studio happens to be working fine with this proj but mine doesn't. i kept getting those error.. even wen i created a new asp.net proj in vs.net AND send it ova to my frien, it works ova there. but wen he send me back the same file i've sent him, i can't open it in my com.. the thing is it happens to me and most of my other frien.. but not my proj partner. my proj partner keeps his com with the latest windows update. cud it be IIS prob? but we both using version 5.1.. n my frien didnt have any windows update 2 days ago. why?????????? or cud it be cause of .net framework service pack1? Chris
I'm sure this is a porting problem and has something to do with the path in .sln file. You may want to try trick from my earlier message. You will be able to get rid of the problem if you create a new solution and then cut, copy ,paste the code. DONOT add existing project. Create new files, new references... If this works than it is definitely the path problem Hope this works... ---------- user9 A student knows little about a lot. A professor knows a lot about little. I know everything about nothing.
-
Go to settings - control panel - administrative ... there you see Microsoft .NET Framework X.X Wizards etc. if you see 2.0 then u have it
erm nope, we are both using .net framework 1.1.. but my frien did updated his .net framework 1.1 to .net framework 1.1 service pack 1 but i didnt.. however he updated it on the 16 april, n during then we didnt have any problem..
-
erm nope, we are both using .net framework 1.1.. but my frien did updated his .net framework 1.1 to .net framework 1.1 service pack 1 but i didnt.. however he updated it on the 16 april, n during then we didnt have any problem..
-
There are actually many reasons. MSDN it up. The most common I may say is when the path specified in the solution file .sln doesn't match. Edit the following entry in the solution file to match your directory structure. Project("{Some Hex Key}") = "SolutionName", "http://localhost/SolutionName/SolutionName.csproj PS: Solution Name is the the name of your solution. ---------- user9 A student knows little about a lot. A professor knows a lot about little. I know everything about nothing.
sORRY Regarding the Project("{Some Hex Key}") = "SolutionName", "http://localhost/SolutionName/SolutionName.csproj where shld i put this code and what u mean by Some Hex Key and where shld i put the code in
-
sORRY Regarding the Project("{Some Hex Key}") = "SolutionName", "http://localhost/SolutionName/SolutionName.csproj where shld i put this code and what u mean by Some Hex Key and where shld i put the code in
This is XML file contained in the application directory. The default file name will be named YourProjectName.sln (eg. WebApplication1.sln). Edit the attribute there. The Hex key is generated by VS.NET Donot worry about it. Just make sure the path is fine. If nothing works, create new project and Ctrl-C and Ctrl-V the code. This should work. And if this works it is for sure the porting problem. ---------- user9 A student knows little about a lot. A professor knows a lot about little. I know everything about nothing.