As far as I can work out I should be able to copy a web project/application to my IIS Web server and be able to see it as I do when designing it on my development computer.
The problem is once I copy the folder over to my web server and then try to view it the browser it says Error 404 not found. There must be a real simple fix for this. I would like to be able to develop ASP.NET sites using the Visual Web Developer instead of Dreamweaver but this little issue is stopping me. Any ideas?
Cheers,
Darren Woolway
You can't just copy over the files and expect it to run. You have to do a little more work than this.
please see the following;
non iis7: http://support.microsoft.com/kb/323972
iis7: http://learn.iis.net/page.aspx/37/deploying-web-sites-on-iis-7/
Related
I'm having issues debugging my ASP.Net web application. I am trying to debug it through our local network. I picked "Use custom web server" under the properties --> web section and I set the specific page to the path to the page that I'd like to see on that server. However, I keep getting "IIS does not list a web site that matches the launched URL" all the time. Everyone else on the network have no trouble debugging with exactly the same configuration.
Thanks a lot for your help
I finally figured it out. To get it to debug finally I went to IIS Manager. Navigated to my site and selected .Net compilation. There I had to switch the behaviour to debug and it all started working.
Just for others who find this page, I thought I'd add what worked for me. In my case, it was none of the above. I'd just forgotten to run Visual Studio as Administrator.
In Framework 4.0 I have a little console app. I have a self-contained .aspx page (no codebehind) and would like to run the console app just to host this page. I searched around for tricks with System.ServiceModel.Web or System.Web.Services trying to find a way to do this.
Can anyone help me get clue?
Thanks.
Have you seen this article? It's not written for asp.net 4.0, it's written for asp.net 2.0, but I don't think there's much difference.
The easiest way to host ASP.NET on a simple web server is to use the Cassini web server, which you can download from MS, including source code. The following two links help:
http://en.wikipedia.org/wiki/Cassini_Web_Server
http://www.asp.net/downloads/archived-v11/cassini
After downloading, the only things you need to do are:
Comment out lines 92 through 96 of request.cs such that Cassini does not discard
requests coming from hosts other than localhost.
Run build, which builds and installs the Cassini library into the GAC.
Run the server.
Note: Cassini is a Console app, which just happens to show a form. If you're interested in it working purely as a Console app, refactor and remove the form. It should not be hard.
Hey guys, I'm having a super weird problem with my VS 2008 solution.
We had this hand-coded ASP.NET compiled web app on our old IIS6/Win2003 server, working great, moved it to our new IIS7/Win2008 server, still working great, but when I try to compile the application and publish it again to our new Win2008 server, I get server 500 errors. It's ASP.NET 2.0 with AJAX extensions and AJAX control toolkit.
I'm not too great with server issues, or even sure if it is a server issue but here are some more symptoms... ?
I know the website works (it only differs by some minor code fixes) and can use it's code on a development machine, there are no errors, and it publishes fine. Publishing (using the DLL files), and even not publishing and trying to use the code-behind files on our new server, both no success. The old website does work on the new server just fine.
If I put a simple hello world html page in the website's virtual directory, with the old code, it works fine, but with the new code, that html page gets the 500 error. And in fact, oddly, I can add all the files to the website, only when I add the web.config, do I get the 500 error. The web.config has not changed.
Tried stopping and restarting IIS
What's the problem, here? Any ideas, what else can I do to troubleshoot the problem?
Check what IIS7 is running under .NET 2.0 or .NET 3.5?
Its tough to see without being there, have you checked which App pool the server is running the site on? (default should be OK, I have found some to be set to classic which causes problems with the AJAX control toolkit)
Also you could try aspnet_regiis -i (if the server is 64 bit make sure you run the one under the 64 bit version of .net)
It was a IIS 7 to 8 issue.
Both machines have different assemblies that need to be just-so on the web.config, in addition with IIS7 web.config changes to make AJAX happy (it has new XML sections).
I'm not a web developer, so what seems weird to me is hopefully an easy one.
Have an existing ASP.NET web site which I need to modify, using VS 2008. I worked on an aspx page and somehow the CSS settings changed and messed the page up badly. I restored the old CSS files and now the page is fine again in the IDE but still a mess when I run the project.
Any ideas would be much appreciated
Steven Segal
Have you tried clearing your browser's cache?
Could it be, that website needs authentication (i.e. FormsAuthentication) ?
If so, the Visual Studio ASP.NET Development Server also blocks css files and images making your web app look like crap in Visual Studio... IIS however doesn't have this behaviour, so when you deploy your site, all looks nice and tidy...
I haven't used Visual Studio since VB 3 and am trying to give it a shot with ASP.NET. It seems that it should be able to connect to a website (via some sort of ftp like protocol I figure) and allow to edit without having to manually upload/download the files. Is this the way it is supposed to work or am I mis-understanding? I have tried using 'create new website' and 'open website' using my testing domain (hosted by godaddy, wondering if that may be the issue as well), each time it gives me errors. I'm not sure if I'm doing something wrong or trying to do something it wasn't meant to.
You really don't want to be working directly on a live web site, do you? That's just crazy. One little mistake and you've hosed the site.
Visual Studio now has it's own built in web server. You use that for testing. If you really don't want to use that you can put IIS on your local machine or set up a Dev/QA server somewhere. In that case, you'd edit it via a file share.
You should be using some kind of source control. Even for a single developer it's very important. When finished with a programming session, you check your updates back into source control.
Finally, only after the site's gone through a suitable QA process, the production server is updated from source control, not from within visual studio.
I would develop your website locally and ftp it to your godaddy website after or use the publish website feature in VS