I have developed a website using Asp.Net MVC which uses a SQL CE database in the App_Data. The website when run in Visual Studio, runs fine. But, when i opened it as 'site from folder' in Microsoft WebMatix. It doesn't show anything. In IE it says "Internet Explorer cannot display the webpage" and in chrome it says " Chrome could not connect to localhost:49742".
This happens on the url, where database access is performed. Basic pages work.
I tried opening other website(MvcMusicStore) using 'site from folder' and it works fine. Why does it happen in the above case when everything is similar. I cannot do the debugging since it is not happening in visual studio
It probably doesn't work because you don't have configured your site with IIS (or another webserver like Cassini).
Probably while in visual studio you have configured your project to use "visual studio development server" with "Auto-assign port". If yes, it's visual studio that starts your web server every time you press F5.
Related
I cannot use VS2013 due to the fact that the "Visual Studio Development Server" option is missing. You can only use IIS Express, or an external host. When I use IIS Express, I get one of several errors when I launch a website with F5.
Failed to register URL "" for site "" application "/". Error description: Cannot create a file when that file already exists. (0x800700b7)
Cannot process request because the process (8204) has exited.
Neither of them make sense. I tried deleting all the configured sites in the IIS express config. I tried reinstalling IIS Express, Visual Studio. I don't see how the first error can occur. In all the demos I've seen, you can just hit F5 in VS and it works. This isn't the case here.
Right click on the Project in your solution and pick Properties.
Select web on the left side.
Choose IIS Express
Enter Project url
example:
https://localhost:44300
or you could check 'Override application root url' and type url like above
I have a classic ASP website deployed over IIS.
I am opening that website from the same location in visual studio 2010 (in order to debug, as per the steps mentioned here
The problem is that, when I hit F5 in visual studio it is giving me an error saying "your server does not support debugging of asp net or atl..."
I am able to browse the site from IIS, but I want to open it in Visual Studio in order to debug it.
What could be the possible reason and solution of this issue?
F5 doesn't do anything good for classic ASP sites (f5 will try to compile a .NET site and then access it).
I will assume that you are trying to debug the site on the same machine where it's running. The way you debug "classic" ASP using Visual Studio.NET is by attaching to the process running the site. The easiest way to do this is to use the Just In Time (JIT) feature: insert a stop statement in the code (debugger in jscript) - hitting that line should initiate a server-side "Error of type "Script Debugging" was encountered. Do you want to debug?" dialog, with suggestions of available debuggers to use.
Try this and report what happens - there might be some extra steps needed to configure that machine.
Are you using IIS 7?
If so you should the server option "Enable server side debugging"... It should be in the properties window of the site, using IIS Management Console.
Once you do that, when you run the server through Visual Studio, it should open another solution on debugging mode with the relevant code.
I'm developping site in webmatrix. I was having some trouble with my variables and database insert so decided to try debugging using visual studio (from the webmatrix launch button).
When I run the site from visual studio it just shows me the directory listing.
the URL is: http://localhost:50051/learning/
When I run the same page from webmatrix it is fine.
The URL is: http://localhost:31430/Default.cshtml
I can see that the localhost number is different and that the visual studio one is not pointing to the default page but just the the root folder. But I don't know how to fix it.
Easiest solution...right mouse click on the web site project in Visual Studio and click on use IIS Express and run again.
I have read this question and this page linked to in the question, as well as dozens of other articles about debugging asp classic with VS but it's still not clicking for me.
I am using VS 2010. The files I want to debug live on a remote server. I have installed the Remote Debugger on the server. I opened the website and attached to the w3wp.exe process on the remote machine. I created some breakpoints but I am still getting "The breakpoint will not currently be hit. No symbols have been loaded for this document" on those breakpoints. Is that the problem or is that a symptom of a larger problem with what I am doing?
First, by default, when you open a web site in Visual Studio, you're opening it via the file system, not via IIS. If this is the case, then Visual Studio uses the internal Cassini web server, rather than IIS.
The Cassini web server does NOT run classic ASP. IIS does. So the first thing you need to do is figure out how to debug in IIS.
It should go without saying, you need to have IIS installed on the machine you're working with, and have the web site you're debugging set up the same as it would be on the server. (so you should be able to run http://localhost/somepath and be able to see your site)
You also need to attach to the running process of Internet Explorer. There's a link to that as well.
Next, you need to get Visual Studio to attach to IIS and execute the web site rather than use the built-in web server and enable debugging.
That's covered here: This topic is no longer available (which is the first child link of the page you liked to in your question here.
From there, you should be able to follow the remaining links and get up and running.
Edit - added
This article takes you through it step-by-step.
Debugging Classic ASP ( VBScript ) in Visual Studio 2008
I've just had this problem when trying to debug a classic ASP application in VS2012.
There's no need to copy PDB files, because there aren't in this kind of projects, so follow this steps:
Be sure that ASP compatibility is turned ON in your IIS installation (Control Panel -> Enable/Disable Windows features -> Internet Information Server). You can install all features if you want to be sure.
Access to the IIS administration.
Locate your WebSite, then access the ASP configuration.
Find "Debugging properties" and then enable client and server debugging. You can also enable error sending to the browser.
After that, just attach the VS2012 debugger to the "w3wp.exe" process. DEBUG -> Attach to process....
This will work for local debugging. If you want to do remote debugging, you must prepare the remote server to allow remote debugging (TIP: Use the same user in both, server and your machine, and be sure it has enough privileges). For more information take a look at:
Installing the Remote Tools
Debugging Classic ASP ( VBScript ) in Visual Studio 2008
Here is my environment
Windows7, Visual Studio 2010, MVC2.0 and NET4
My default web site is configured to use ASP.NET v4.0 application pool.
Here is an easy way to reproduce my problem
Create a new MVC2 application
Open the properties Window
Go to the Web tab
Check "Use IIS Local Web Server"
Click on "Create Virtual Directory" button
I get this error message
To access local IIS Web Sites, you must install the following IIS components:
In addition, you must run visual Studio in the context of an Administrator account
For more information, press F1
Notice the blank line after "...the following IIS components:"
I am running VS2010 as administrator
Pressing F1 does not bring any help
I checked my Windows eventlog files and found that my metabase was corrupted
(I thought we get rid of this in IIS7 but it looks like it is still here...)
I used this Microsoft article to restore it from an old version and now everything is working
Hope this can help somebody else
Have you tried running VS as administrator?
Right click your VS shortcut and select "Run as Administrator"
I had the same error message, in my case with VS2008, Windows 7 + IIS7, when trying to add an existing web site to a solution. I think this is one of those error messages where what it states can be a big red herring, i.e. it doesn't necessarily have anything to do with running as an administrator or not having components installed.
In my case, the web site had an HTTP binding in which the hostname was set to "localhost". Once I cleared that, it worked fine. Don't ask me why I put "localhost" in there, it just seemed to make sense at the time.
My internet hunting also turned up this brief entry, which did not work for me.