Server.CreateOb ject Vs CreateObject

[Sagar]

I am working on a project where Server.CreateOb ject is replaced with
CreateObject all over the project. Though I know that this will
improve performance in terms of Memory overlhead because of how the
object creation happens with Server.CreateOb ject, I would like to
create 'visible scenarios' that i create with code to show people that
'"look. here's the difference". Is it possible ?

I will create a page with 2 calls, 1 with Server.CreateOb ject and 1
with CreateObject, run the code and see the difference. Any thoughts ?
Thanks.
Anand.

[Anthony Jones]

"Sagar" <an********@gma il.comwrote in message
news:d6******** *************** ***********@1g2 000hsl.googlegr oups.com...

I am working on a project where Server.CreateOb ject is replaced with
CreateObject all over the project. Though I know that this will
improve performance in terms of Memory overlhead because of how the
object creation happens with Server.CreateOb ject, I would like to
create 'visible scenarios' that i create with code to show people that
'"look. here's the difference". Is it possible ?

I will create a page with 2 calls, 1 with Server.CreateOb ject and 1
with CreateObject, run the code and see the difference. Any thoughts ?

I've never heard of any significant memory usage difference between the two
and I find it difficult to see what might be the cause of such a difference.

The only real difference between the two is handling of OnStartPage and
OnEndPage methods on the classes default interface.

When using Server.CreateOb ject after the object is instanced ASP looks for
the OnStartPage method on the returned interface, if found it is called with
the current script context as a parameter.

This handling does not occur for CreateObject. However, since IIS 5.0 ASP
runs as a COM+ context and components can implement IObjectContext through
which the scripting context can be discovered. This approach works whether
the Server version is used or not.

Personally I still implement OnStartPage since its a lot less faff but it
does require the use of Server.CreateOb ject.

--
Anthony Jones - MVP ASP/ASP.NET

[Sagar]

Not really. I have read in other sites that there IS a difference.

With Server.CreateOb ject, the object instance is created with the
context of transaction
With CreateObject, the obect is created without any context.

Let me know if this is incorrect.

and Is there a way to demo these scenarions and some simple code ?

Thanks,
Anand.

On Jan 15, 6:35*pm, "Anthony Jones" <A...@yadayaday ada.comwrote:

"Sagar" <anandsa...@gma il.comwrote in message

news:d6******** *************** ***********@1g2 000hsl.googlegr oups.com...

I am working on a project where Server.CreateOb ject is replaced with
CreateObject all over the project. Though I know that this will
improve performance in terms of Memory overlhead because of how the
object creation happens with Server.CreateOb ject, I would like to
create 'visible scenarios' that i create with code to show people that
'"look. here's the difference". Is it possible ?

I will create a page with 2 calls, 1 with Server.CreateOb ject and 1
with CreateObject, run the code and see the difference. Any thoughts ?

I've never heard of any significant memory usage difference between the two
and I find it difficult to see what might be the cause of such a difference.

The only real difference between the two is handling of OnStartPage and
OnEndPage methods on the classes default interface.

When using Server.CreateOb ject after the object is instanced ASP looks for
the OnStartPage method on the returned interface, if found it is called with
the current script context as a parameter.

This handling does not occur for CreateObject. *However, since IIS 5.0 ASP
runs as a COM+ context and components can implement IObjectContext through
which the scripting context can be discovered. *This approach works whether
the Server version is used or not.

Personally I still implement OnStartPage since its a lot less faff but it
does require the use of Server.CreateOb ject.

--
Anthony Jones - MVP ASP/ASP.NET

[Jon Paal [MSMD]]

You may need to ask the IIS folks as they may know of recent issues regarding this matter.

An example of an iis issue :

http://support.microsoft.com/default.aspx/kb/193230