|
Home > Archive > Commerce Server General > July 2006 > Pipeline Component: ATL vs C#
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Pipeline Component: ATL vs C#
|
|
| Ever Olano 2006-07-13, 1:18 pm |
| Hello. I posted a similar question yesterday but I thought I needed to
rehash my questions now that I've read more.
We have an existing pipeline component that we wrote for CS2002. While,
after reading the docs, it seems it will work fine on CS2007 (except maybe
for some order schema issues, true? or is the new order schema fully
backwards-compatible?), I'm trying to weigh the pros and cons of rewriting it
in C#.
Is a C#-written pipeline component any better than an ATL one? Or is it
just a matter of language preference? Would writing it in C# allow me to
access objects that I wouldn't normally be able to access easily or at all in
my C++ code?
The way I see it though, it might be slower as Commerce Server would shift
from CLR (ASP.NET) to COM (pipeline) and back to CLR (the pipeline
component). Or is that negligible?
Thanks in advance for any inputs.
Ever
| |
|
| I'd say it's just a matter of taste to use ATL or C#. There should not be any
difference between the objects you can use.
From the performance point of view, I think that ATL component could perform
better since the from the documentation I states that the pipeline is
managing the objects as COM objects and thus it needs CLR interop to access
C# (and all the pipeline management functions I have found are wrapped in the
Microsoft.CommerceServer.Interop.dll assembly) components . ATL objects do
not need any interop since they are already "native" COM objects anyway.
"Ever Olano" wrote:
> Hello. I posted a similar question yesterday but I thought I needed to
> rehash my questions now that I've read more.
>
> We have an existing pipeline component that we wrote for CS2002. While,
> after reading the docs, it seems it will work fine on CS2007 (except maybe
> for some order schema issues, true? or is the new order schema fully
> backwards-compatible?), I'm trying to weigh the pros and cons of rewriting it
> in C#.
>
> Is a C#-written pipeline component any better than an ATL one? Or is it
> just a matter of language preference? Would writing it in C# allow me to
> access objects that I wouldn't normally be able to access easily or at all in
> my C++ code?
>
> The way I see it though, it might be slower as Commerce Server would shift
> from CLR (ASP.NET) to COM (pipeline) and back to CLR (the pipeline
> component). Or is that negligible?
>
> Thanks in advance for any inputs.
> Ever
>
>
>
|
|
|
|
|