Re: ASP.net client using Local .dll instead of remote
From: Ken Kolda (ken.kolda_at_elliemae-nospamplease.com)
Date: 12/10/04
- Next message: Stefan Rosi: "Accessing WebService indirectly"
- Previous message: alanschoeff: "ASP.net client using Local .dll instead of remote"
- In reply to: alanschoeff: "ASP.net client using Local .dll instead of remote"
- Next in thread: alanschoeff: "Re: ASP.net client using Local .dll instead of remote"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 9 Dec 2004 16:20:19 -0800
When the client is an ASP.NET app, you should put your remoting
configuration settings in the web app's web.config file instead of a
seperate config file. It will be then be read automatically when the web app
starts.
Give that a shot and see if that fixes your problem.
Ken
"alanschoeff" <alanschoeff@hotmail.com> wrote in message
news:1102612634.362382.31100@z14g2000cwz.googlegroups.com...
> I have a relatively simple web page running on my localhost winxp pro
> iis6.0 development pc.
>
> I have a relatively simple remote object hosted in IIS on a separate
> server. I have a web.config file in the root directory of the virtual
> directory and the object is in the bin directory.
>
> I have a copy of the remote object .dll in my application bin
> directory. I have a client.config file in my applicaiton root
> directory. I have remoting=on in my application's web.config file.
>
> in the application global.asax application_start event, I have
>
> Dim ltmp As String = Server.MapPath("Client.config")
> RemotingConfiguration.Configure(ltmp)
>
> but the web app always runs the local copy of the .dll file and never
> runs the remote copy. any thoughts would be nice.
>
> client.config
>
> <configuration>
> <system.runtime.remoting>
> <application>
> <channels>
> <channel ref="http">
> <clientProviders>
> <formatter ref="binary" />
> </clientProviders>
> </channel>
> </channels>
> <client>
> <wellknown
> url="http://IP_ADDRESS HERE/IBDPRRemoteLIB/RptDataLayer.rem"
> type="CA_RptCrd_Lib.RptDataLayer, CA_RptCrd_Lib"
> />
> </client>
> </application>
> </system.runtime.remoting>
> </configuration>
>
> remote library web.config
> <configuration>
> <appSettings>
>
> <add key="IBDPRConnString" value="User ID=IBDPR;Password=1220;Data
> Source=ODSDEV;" />
>
> </appSettings>
>
> <system.runtime.remoting>
> <application>
> <service>
> <wellknown
> mode="SingleCall"
> type="CA_RptCrd_Lib.RptDataLayer, CA_RptCrd_Lib"
> objectUri="RptDataLayer.rem"
> />
> </service>
> <channels>
> <channel ref="http">
> <serverProviders>
> <formatter ref="binary" />
> </serverProviders>
> </channel>
> </channels>
> </application>
> </system.runtime.remoting>
> </configuration>
>
- Next message: Stefan Rosi: "Accessing WebService indirectly"
- Previous message: alanschoeff: "ASP.net client using Local .dll instead of remote"
- In reply to: alanschoeff: "ASP.net client using Local .dll instead of remote"
- Next in thread: alanschoeff: "Re: ASP.net client using Local .dll instead of remote"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|