I hate that monster! The features are good but the usability is rubbish. Of course, fiding a good alternative is difficult, since most others don't offer either of the two (usability + features). However, after a month of searching, I found Visual Paradigm for UML, which is much better from a usability standpoint and still offers good features. I recommend it.

I know what the error is but what I want is to see the filenames and line numbers on compile.

Yes. There are no filenames or line numbers there, either.

I believe this is a security feature - you cannot hide the URL.

When I compile my ASP.NET website in Visual Studio, it does not give me any file/line information for the errors. Thanks to this, I cannot know where these errors even are. How can I make it show error locations?

------ Build started: Project: C:\...\Veebileht\, Configuration: Debug .NET ------
Validating Web Site

(0,0): error CS0103: The name 'KasutajaõigusteSüsteemiKonfiguratsioon' does not exist in the current context
(0,0): error CS0103: The name 'KasutajaõigusteSüsteemiKonfiguratsioon' does not exist in the current context
(0,0): error CS0103: The name 'KasutajaõigusteSüsteemiKonfiguratsioon' does not exist in the current context
(0,0): error CS0103: The name 'KasutajaõigusteSüsteemiKonfiguratsioon' does not exist in the current context
(0,0): error CS0246: The type or namespace name 'StruktuuriElement' could not be found (are you missing a using directive or an assembly reference?)
(0,0): error CS0103: The name 'StruktuuriElement' does not exist in the current context
Validation Complete

I would like to configure VS to use a remote IIS server for debugging a .NET 3.5 web application. How do I do this? Everything I find on the web claims that I just have to set some properties in the project configuration under the debugging tab to point to the right server. However, there is no Debugging tab. Under the Web tab, I only seem to be able to specify a local IIS server, not a remote one. I also found one guide that said VS will automatically publish/deploy my application before debugging. This would be very useful but I also do not have a Deployment tab which this guide referred to. I assume these guides were for VS2005 or earlier? They did not specify. How can I accomplish what I want? Ideally, VS would also publish the application before opening it for debugging. (Search keeps giving me the "No error" error, so my apologies if this is an often-asked question)