Re: Length of an if statement in dotnet (migrating from asp to asp.net)

Tech-Archive recommends: Fix windows errors by optimizing your registry

me_at_privacy.net
Date: 05/27/04 

Date: Thu, 27 May 2004 15:28:15 -0400

It is somewhat of a maintenance problem, but I wasn't sure if it was the
cause of the problem I'm having.

My reason for not recoding it at this point was if it wasn't a problem (i.e.
the thing that was now breaking the app in dotnet), I didn't want to waste
time fixing it & it not be what was wrong.

If I take out this file from the dotnet application, it will execute; if I
put it in, it will not. The only thing that jumped out to me on this was
the length of the if statement in this module. All the if's and end if's
match up, everything else looks pretty normal.

SC

"Matt Berther" <mberther@hotmail.com> wrote in message
news:OTAmJwBREHA.2572@TK2MSFTNGP12.phx.gbl...
> Hello jai,
>
> No, but dear God isnt that a maintenance nightmare? Why wouldnt you
refactor that as soon as possible?
>
> > I have a module that's processed as an include file in a tradtional
> > asp application that I'm migrating to dotnet.
> >
> > In one of the modules, there's an if statement that's gotten appended
> > to over the years it's been in production, that when it's been
> > translated into dotnet, the if statement (if..... then) itself is
> > several hundred characters long.
> >
> > The original statement was similar to:
> >
> > if session("rpt") = "X1" and (session("user") = "User1" or
> > session("user") = "User2".....
> >
> > which has now become
> >
> > if session("rpt").ToString() = "X1" and (session("user").ToString() =
> > "User1" or session("user").ToString() = "User2".......
> >
> > Is there a max length that the if statement can be?
> >
> > SC
> >
> --
>
> --
> Matt Berther
> http://www.mattberther.com