Compiler warnings and performance

  • Thread starter Thread starter cashdeskmac
  • Start date Start date
C

cashdeskmac

Hi,

I have built an application containing a few projects (nothing that I have
written)and there are a few compiler warnings (obsolete methods and the like).

Does anyone know if these obsolete methods cause any performance issues if
not corrected? I would imagine that they do, but would be interested to know
to what extent.
 
Hi,

I have built an application containing a few projects (nothing that I have
written)and there are a few compiler warnings (obsolete methods and the like).

Does anyone know if these obsolete methods cause any performance issues if
not corrected?  I would imagine that they do, but would be interested toknow
to what extent.
Click to expand...

IMHO, I think performance concerns should be the least of your worries
if you have code with obsolete warings.
I would have to assume there isn't any way to measure performance
using obsolete api's on a machine with multiple .NET runtimes.
 
As I said, it wasn't code that I had written. This is part of an application
containing over 380 projects and which has been upgraded from v1.1 to v3.0 in
the last few months. It has also had an upgrade to a third party data
retrieval layer and it is this which is creating all of the obselete method
warnings. As is often the case, though, there is no money to pay for a clean
up of the code, so things will probably be left as they are.
 
Back
Top