Missing Deprecated Warnings

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • David

    #1

    Missing Deprecated Warnings

    When I did some trial conversions of a .Net 1.1 c# web app earlier this year
    I got the expected Deprecation warnings, e.g. for
    Page.RegisterSt artupScript. Now I am doing the real conversion and the first
    thing I notice is that I am not getting any warnings, even though the
    Page.RegisterSt artupScript calls are still there. I know about those, so I
    can find and fix. But there could be other usages of deprecated methods that
    I donlt know about.

    I've looked for compiler settings that might stop the warnings being
    generated, but can't find anything.

    Any ideas woudl be much appreciated

    Dave


  • Cor Ligthert[MVP]

    #2
    Re: Missing Deprecated Warnings

    David,

    Are you sure that your explorer error warnings are not set off by any kind
    of automatic upgrade, something that I have the idea that happened at least
    once to me?

    Cor

    "David" <davidh@NOSPAM2 3dantedsystems. co.ukschreef in bericht
    news:iqdKi.2237 1$BW4.21105@fe1 .news.blueyonde r.co.uk...
    When I did some trial conversions of a .Net 1.1 c# web app earlier this
    year I got the expected Deprecation warnings, e.g. for
    Page.RegisterSt artupScript. Now I am doing the real conversion and the
    first thing I notice is that I am not getting any warnings, even though
    the Page.RegisterSt artupScript calls are still there. I know about those,
    so I can find and fix. But there could be other usages of deprecated
    methods that I donlt know about.
    >
    I've looked for compiler settings that might stop the warnings being
    generated, but can't find anything.
    >
    Any ideas woudl be much appreciated
    >
    Dave
    >

    Comment

    • David

      #3
      Re: Missing Deprecated Warnings

      Hi Cor

      Thanks for replying. My problem is that I am not getting the "deprecated "
      warnings when I should.
      I can;t find a way to turn them on - they should be on by default I think.

      David

      "Cor Ligthert[MVP]" <notmyfirstname @planet.nlwrote in message
      news:8AE6CDE6-1250-4F14-BB4A-C9C7DF6E967F@mi crosoft.com...
      David,
      >
      Are you sure that your explorer error warnings are not set off by any kind
      of automatic upgrade, something that I have the idea that happened at
      least once to me?
      >
      Cor
      >
      "David" <davidh@NOSPAM2 3dantedsystems. co.ukschreef in bericht
      news:iqdKi.2237 1$BW4.21105@fe1 .news.blueyonde r.co.uk...
      >When I did some trial conversions of a .Net 1.1 c# web app earlier this
      >year I got the expected Deprecation warnings, e.g. for
      >Page.RegisterS tartupScript. Now I am doing the real conversion and the
      >first thing I notice is that I am not getting any warnings, even though
      >the Page.RegisterSt artupScript calls are still there. I know about those,
      >so I can find and fix. But there could be other usages of deprecated
      >methods that I donlt know about.
      >>
      >I've looked for compiler settings that might stop the warnings being
      >generated, but can't find anything.
      >>
      >Any ideas woudl be much appreciated
      >>
      >Dave
      >>
      >

      Comment

      Working...