Why xml line highlighted yellow in IDE?

[Member 96]

I'm just starting out with C# and I'm following one of the Microsoft walkthroughs for creating a distributed application. It involves IIS, SQL server and a windows client and a web client. The windows client works fine, but the web client just times out so I was poking around trying to find out what's going on because there are no obvious problems (aka I don't know really what to look for :-D). Anyway, the question I have is when I switch to HTML view for my web form, the first line of xml code is highlighted in yellow, the line is (not broken in the original, just one line): <%@ Page language="c#" Codebehind="WebForm1.aspx.cs" AutoEventWireup="false" Inherits="WebApplication1.WebForm1" %> Is this to indicate an error or parsing problem of some kind or....? The full code for the form is this: <%@ Page language="c#" Codebehind="WebForm1.aspx.cs" AutoEventWireup="false" Inherits="WebApplication1.WebForm1" %> WebForm1

[Furty]

It's 100% normal for it to be highlighted yellow. The yellow highlighted lines in asp.net pages are lines that specify the backend library for the page.

[Member 96]

Thank you Furty. That rules that out as pointing to the problem. I guess I'm going to have to do some digging to figure out how to debug a web application. Thanks again

[Atul Kale]

Hi there, I just thought this information might be useful to u! Though from ur mail it sounded like u r just beginning ASP.NET, I would not try and offend u by giving some information that u already know! If it helps, GREAT! Debugging a web Application fortunately is much better in VS.NET than it was in InterDEV with ASP. A process named ASPNET_WP.exe runs on the machine within which your ASP.NET (C# or VB.NET) code is debuged. If your solution contains several projects, just set up any of the desired projects as a Startup Project from the Context menu, and any of the aspx pages as the startup page. If your machine's config is very good, you will go for this traditional debugging approach which is good too! But, there is a better approach wherein, you just open any desired page in the Browser, and at any point of time Go into Debug mode by Attaching to the ASPNET_WP.exe process from Tools->Debug Processes menu option. just go ahead with the default options while doing this. Hope htis helps a bit! :) Atul kale Sr. Software Engineer XcelVision Technologies Ltd.

[David Stone]

Are you debugging remotely or locally?

---

Hey, what can I say? I'm a chick magnet...a babe conductor...a logarithm for the ladies. -Strong Bad from HomeStarRunner.com Essential Tips for Web Developers

[Member 96]

Hi Atul, that information is extremely helpful, thank you very much! Cheers!

[Member 96]

Hi David, I'm debugging remotely if you consider the computer sitting 6 inches to the left of my development system remote. From what I understand (and have done) since reading Atul's message is that you can debug locally if you have installed VS.NET after you installed IIS etc as it adds debugging support, however, as in my case, you need to run the STEP 1 of the vs.net setup on the remote IIS server, then do STEP 2 of the VS.NET setup selecting only the server / remote debugging components which takes care of all that. (it's in the readme file for VS.NET installation). (Although you may already know all this;))