«

naming a webform Object.aspx, creates a class called Object, which will hide
the System.Object class, and cause some problems. Stay away from naming
stuff the same as System classes.

-- bruce (sqlwork.com)


"john_ca @hotmail.com>" <john_murray_sp<remove> wrote in message
news:180CB9D2-EEDD-4246-8D5F-...
> Added a Webform to existing project and named the file "Object.aspx".
>
> After that the Global.asax did not load (or at least the 'Session_start'
method did not fire). This occured both with running the application or
debugging from within Visual Studio (e.g. breakpoint within Session_start
was not hit).
>
> Removed the offending file and all was well.
>
> Any thoughts?
>
>
> Environment:
> Windows 2000 SP3
> .NET Framework version v1.1.4322
> Visual Studio .NET 2003
> IE 6.0.2800.1106
>

I believe it should not be the problem.
Since it's only humans understand Short Names.
Compiler always compiles with fully qualified name like System.Object and
there is no way that runtime will confuse MyProject.Object with
System.Object.

But i lived long enough to know that everything is possible
But i would check twice before accept this theory.

George.


"bruce barker" <> wrote in message
news:...
> naming a webform Object.aspx, creates a class called Object, which will
hide
> the System.Object class, and cause some problems. Stay away from naming
> stuff the same as System classes.
>
> -- bruce (sqlwork.com)
>
>
> "john_ca @hotmail.com>" <john_murray_sp<remove> wrote in message
> news:180CB9D2-EEDD-4246-8D5F-...
> > Added a Webform to existing project and named the file "Object.aspx".
> >
> > After that the Global.asax did not load (or at least the 'Session_start'
> method did not fire). This occured both with running the application or
> debugging from within Visual Studio (e.g. breakpoint within Session_start
> was not hit).
> >
> > Removed the offending file and all was well.
> >
> > Any thoughts?
> >
> >
> > Environment:
> > Windows 2000 SP3
> > .NET Framework version v1.1.4322
> > Visual Studio .NET 2003
> > IE 6.0.2800.1106
> >
>
>

I agree. But in any case, Microsoft should save us from ourselves (and our mis-guided naming decisions). The compiler should warn us that it cannot resolve the name..

I still think it's a bug, and with interesting behaviour..

----- George Ter-Saakov wrote: ----

I believe it should not be the problem
Since it's only humans understand Short Names
Compiler always compiles with fully qualified name like System.Object an
there is no way that runtime will confuse MyProject.Object wit
System.Object

But i lived long enough to know that everything is possible :
But i would check twice before accept this theory

George


"bruce barker" <> wrote in messag
news:..
> naming a webform Object.aspx, creates a class called Object, which wil
hid
> the System.Object class, and cause some problems. Stay away from namin
> stuff the same as System classes
>> -- bruce (sqlwork.com
>>> "john_ca @hotmail.com>" <john_murray_sp<remove> wrote in messag
> news:180CB9D2-EEDD-4246-8D5F-..
>> Added a Webform to existing project and named the file "Object.aspx"
>>>> After that the Global.asax did not load (or at least the 'Session_start
> method did not fire). This occured both with running the application o
> debugging from within Visual Studio (e.g. breakpoint within Session_star
> was not hit)
>>>> Removed the offending file and all was well
>>>> Any thoughts
>>>>>> Environment
>> Windows 2000 SP
>> .NET Framework version v1.1.432
>> Visual Studio .NET 200
>> IE 6.0.2800.110
>>>>