|
Home > Archive > Commerce Server General > October 2005 > Deploying (registering) pipeline components
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 |
Deploying (registering) pipeline components
|
|
| Phil Mellor 2005-10-10, 7:52 am |
| Hello,
I've developed some custom pipeline components in C# for use in a
Commerce Server 2002 deployment. Unfortunately, it's rather awkward
releasing them to our test and production servers because of the
registration process:
1. Register the library (either by compiling with Visual Studio .NET or
using regasm.exe)
2. Register the pipeline components using pipereg.exe
3. Modify the pipelines using the pipeline editor - remove the broken
components and add them again.
I suspect the underlying problem is that the class ID for each
component changes when the library is rebuilt, and so requiring
re-registration.
Is it possible to automate the registration, or to avoid re-registering
the components?
Cheers,
Phil Mellor
| |
| Nihit Kaul [MSFT] 2005-10-24, 10:38 am |
| Hi Phil,
I don't think you need to do step 3 => If the component is registered
correctly, the pipelines can be executed directly without editing them.
Also - for step 2, you can export out the registry keys to be modified and
simply run the *.reg file on the server, instead of running the whole
pipereg.exe tool through the UI.
Step 1 cannot obviously be avoided, but the rest should be fairly
automatable if you wish to do so (running the reg file that is).
Thanks,
Nihit Kaul[MSFT]
Commerce Server
http://blogs.msdn.com/nihitk
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
--------------------
From: "Phil Mellor" <riscos@gmail.com>
Newsgroups: microsoft.public.commerceserver.general
Subject: Deploying (registering) pipeline components
Date: 10 Oct 2005 02:04:09 -0700
Organization: http://groups.google.com
Lines: 26
Message-ID: <1128935049.442525.321520@g43g2000cwa.googlegroups.com>
NNTP-Posting-Host: 212.159.65.123
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1128935054 19282 127.0.0.1 (10 Oct 2005
09:04:14 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Mon, 10 Oct 2005 09:04:14 +0000 (UTC)
User-Agent: G2/0.2
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; SV1;
.NET CLR 1.1.4322; .NET CLR 1.0.3705),gzip(gfe),gzip(gfe)
X-HTTP-Via: 1.0 NEW_LEGOLAS
Complaints-To: groups-abuse@google.com
Injection-Info: g43g2000cwa.googlegroups.com; posting-host=212.159.65.123;
posting- account=28OfCQ0AAACmElYmhsliLl1Zcb8OVAyb
Path:
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.
sul.t-online.de!t-online.de!news.glorb.com!postnews.google.com!g43g2000cwa.g
ooglegroups.com!not-for-mail
Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.commerceserver.general:17028
X-Tomcat-NG: microsoft.public.commerceserver.general
Hello,
I've developed some custom pipeline components in C# for use in a
Commerce Server 2002 deployment. Unfortunately, it's rather awkward
releasing them to our test and production servers because of the
registration process:
1. Register the library (either by compiling with Visual Studio .NET or
using regasm.exe)
2. Register the pipeline components using pipereg.exe
3. Modify the pipelines using the pipeline editor - remove the broken
components and add them again.
I suspect the underlying problem is that the class ID for each
component changes when the library is rebuilt, and so requiring
re-registration.
Is it possible to automate the registration, or to avoid re-registering
the components?
Cheers,
Phil Mellor
|
|
|
|
|