Windows Server

cliff · Guest

We have a wip process working in dev. And we ran into questions of how to
releasing WIP to QA.

As we know, the WIP dev process starts like:
1. create .net client project, import host definition, then compile to get a
dll.
2. deploy this dll to HIS using TI manager and we will get a remoting proxy
that points back to the component we deployed in HIS just now.
3. then we can import this remoting proxy dll to any web service project and
we can talk from web service to HIS now.

Here comes the question: in step 3, the remoting proxy dll we imported into
our current web service project points back to HIS component in dev
environment, when we release the code to QA, i assume we need to do step 2
again and a new remoting proxy will be created. To make things work, do we
need to remove the old reference to remoting proxy dll and add reference to
the new remoting proxy dll and recompile? It does not sounds a right process
to me, but I check the docmenttion and do find other better idea.

We know that if you import a web reference of web service into your project,
you can make that web reference dynamic, and you can change the url of wsdl
when you migrate code into different environment. I am wondering does HIS has
similar mechanism?

Thanks and any comment and suggeison are welcomed!

Rob Beardsworth [MSFT] · Guest

Hi,
there are 2 possibilities: you can re-administer the object, producing a
new proxy and recompile your client against that, OR you can do what others
have done, which is make your client able to change the URL contained in
the proxy. When you create the TI object in the client, you can change the
"url" property of it to point to your production machine, virtual directory
etc. The proxy inherits from (err, going from memory) RemotingClientProxy
and it's properties can be used to change the destination.

Rob Beardsworth
Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
--------------------
Thread-Topic: .net WIP deployment questions
From: "=?Utf-8?B?Y2xpZmY=?=" <cliff@discussions.microsoft.com>
Subject: .net WIP deployment questions
Date: Mon, 2 May 2005 16:15:01 -0700

We have a wip process working in dev. And we ran into questions of how to
releasing WIP to QA.

As we know, the WIP dev process starts like:
1. create .net client project, import host definition, then compile to get
a
dll.
2. deploy this dll to HIS using TI manager and we will get a remoting proxy
that points back to the component we deployed in HIS just now.
3. then we can import this remoting proxy dll to any web service project
and
we can talk from web service to HIS now.

Here comes the question: in step 3, the remoting proxy dll we imported into
our current web service project points back to HIS component in dev
environment, when we release the code to QA, i assume we need to do step 2
again and a new remoting proxy will be created. To make things work, do we
need to remove the old reference to remoting proxy dll and add reference to
the new remoting proxy dll and recompile? It does not sounds a right
process
to me, but I check the docmenttion and do find other better idea.

We know that if you import a web reference of web service into your
project,
you can make that web reference dynamic, and you can change the url of wsdl
when you migrate code into different environment. I am wondering does HIS
has
similar mechanism?

Thanks and any comment and suggeison are welcomed!

cliff · Guest

Rob, I see what you mean. Your suggestion precisely answered my question.
Thanks again.

"Rob Beardsworth [MSFT]" wrote:

	Windows Server Forum Index -> Host Integration Server	All times are GMT
Page 1 of 1