Comments inline below...
> Hi,
>
[quoted text clipped - 3 lines]
> "gacutil.exe", need I still copy the dll to the IIS "VirtualDir\bin" folder
> for subsequent updates??
If it's in the GAC, it doesn't need to be in the bin folder. But, you should
only put it in the GAC is you need it to be there (e.g. you have other apps
on the same machine which need to use the same assembly).
> Also, I read a book before that if using .NET remoting, client program also
> need the remoting object dll (proxy dll contain interface only) in order to
> run. What is the procedures to generate this proxy dll? I've tried to use
> tlbexp.exe, but seems it does not work when I try to Add Reference!!
Tlbexp.exe is for generating a COM type library, not for generating remoting
proxies. My preferred solution is to create a seperate assembly and define
your interface types in it. Then, reference this assembly in both your
client and server assemblies. Alternatively, you can use the SoapSuds tool
to generate a proxy for your component as long as you're using HTTP/SOAP for
your transport. Just do a search on "soapsuds" on MSDN.
Ken
> Pls help, thx!!
Ming - 24 Dec 2004 12:50 GMT
Hi Ken,
Thx for your reply.
I met a problem using SOAPSUDS.....one of my class have a function which
accept 3 parameters.
However, when I generating the proxy and add a reference to it, compiler
warned me that the function doesn't accept parameters?!
I use:
SOAPSUDS -ia:assembly1 -oa:assemblyProxy.dll
I remember that long long time ago, that function doesn't accept parameter,
but I've changed it already.
Assembly in GAC is update and in the folder where I run SOAPSUDS is also
update.......what probably will be the cause of this problem??
Thx!!
"Ken Kolda" <ken.kolda@elliemae-nospamplease.com> ???g???l???s?D
:u3hiZWR6EHA.2192@TK2MSFTNGP14.phx.gbl...
> Comments inline below...
[quoted text clipped - 29 lines]
>
> > Pls help, thx!!