Visual Studio - Line numbers missing from error list

  • Thread starter Thread starter Greg
  • Start date Start date
G

Greg

Visual Studio - Line numbers missing from error list

I'm writing an app in ASP.NET using VS 2005. There are no line numbers
with the build errors reported. Any suggestions? I can't find any
reports of anyone else having the same problem. Is there a setting I
may have missed?

Greg.
 
Line numbers are available with only debug build. If you deployed to your
serve with Release build, they wont be there?.. Is that case, or is it
missing in Debug build?

VJ
 
Line numbers are available with only debug build. If you deployed to your
serve with Release build, they wont be there?.. Is that case, or is it
missing in Debug build?

VJ
Click to expand...


Thanks for the reply VJ.

The line numbers are missing in Debug build

Greg.
 
you may want to refer to C# or what complier your using and see the
documentation and any available options. I have had no troubles so far, and
VS.NET has made me lazy, so I have not read the complier in detail :-)

VJ
 
Hi Greg,

I'm getting the same thing.
Dunno why.
I've just installed CS2005 AP in the hope that this resolves the issue, but it did not.
I think that its a reinstall of VS2005 next!
Did you manage to track down the issue?

Cheers
Bal

EggHeadCafe.com - .NET Developer Portal of Choicehttp://www.eggheadcafe.com
Click to expand...

Bal,

I've noticed that the problem is specific to my web app - other test
apps I've written haven't had the same problem. Thats all I know at
the moment! So, I don't think reinstalling VS2005 will help at all.

Let me know if you get it sorted!

Thanks,

Greg.
 
Bal,

I've noticed that the problem is specific to my web app - other test
apps I've written haven't had the same problem. Thats all I know at
the moment! So, I don't think reinstalling VS2005 will help at all.

Let me know if you get it sorted!

Thanks,

Greg.
Click to expand...

Bal,

Did you ever resolve this?

I did a "repair" re-installation of Visual Studio last night, still no
success.

Has anyone else found the answer to this problem?

Will a reinstall of Visual Studio definitely resolve the issse?

Greg.
 
Bal,

Did you ever resolve this?

I did a "repair" re-installation of Visual Studio last night, still no
success.

Has anyone else found the answer to this problem?

Will a reinstall of Visual Studio definitely resolve the issse?

Greg.
Click to expand...


I've finally resolved the cause of this problem.

A full reinstall did not work, it just cost me a lot of time.

The answer was the path to the development folder was too long -
moving it up one level solved the problem. I can't understand how
Microsoft can get away with such an obvious bug as this. My company
has spent a lot of money on Microsoft software for the developers, and
to have a problem (with a simple cause) such as this with no
explanation is just unbelievable.

Rant over, but I hope this helps other people in the same predicament.

Greg.
 
Back
Top