RE: Dynamic URL Behavior & Configuration

{\rtf1\ansi\ansicpg936\deff0\deflang1033\deflangfe2052{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\lang2052\f0\fs20 You're welcome.
\par
\par Regards,
\par
\par Steven Cheng
\par Microsoft Online Support
\par
\par Get Secure! www.microsoft.com/security
\par (This posting is provided "AS IS", with no warranties, and confers no rights.)
\par \pard\li720 --------------------
\par Thread-Topic: Dynamic URL Behavior & Configuration
\par thread-index: AcYilF1YQnypYsFySsWvL78NqSxC/w==
\par X-WBNR-Posting-Host: 209.77.204.49
\par From: "=?Utf-8?B?TWlrZSBMaXZlbnNwYXJnYXI=?=" <wally417@xxxxxxxxxxxxxxxxx>
\par References: <193269E2-57C3-44F2-BC55-23C75CDE783A@xxxxxxxxxxxxx> <KRE6HliIGHA.1236@xxxxxxxxxxxxxxxxxxxxx>
\par Subject: RE: Dynamic URL Behavior & Configuration
\par Date: Thu, 26 Jan 2006 08:20:04 -0800
\par Lines: 102
\par Message-ID: <10971C7B-BF16-428D-864A-24F324DB8435@xxxxxxxxxxxxx>
\par MIME-Version: 1.0
\par Content-Type: text/plain;
\par \tab charset="Utf-8"
\par Content-Transfer-Encoding: 7bit
\par X-Newsreader: Microsoft CDO for Windows 2000
\par Content-Class: urn:content-classes:message
\par Importance: normal
\par Priority: normal
\par X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
\par Newsgroups: microsoft.public.dotnet.framework.webservices
\par NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
\par Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
\par Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.dotnet.framework.webservices:13483
\par X-Tomcat-NG: microsoft.public.dotnet.framework.webservices
\par
\par Thank you, Steven. Given your response I looked in the app.config file in the
\par class library project and found the <applicationSettings> and associated
\par section handler entry in <configSections>. I copied those into the
\par executables .config file and now all is working as planned.
\par
\par Mike
\par
\par "Steven Cheng[MSFT]" wrote:
\par
\par > Hi Mike,
\par >
\par > Welcome to MSDN newsgroup.
\par > Regarding on the Webservice proxy with dynamic URL behavior's url string
\par > stroage question, based on my understanding, in vs 2005/.NET 2.0 project,
\par > we still persist the URL string for dynamic behavior webservice proxy in
\par > application config file (app.config or web.config....). yes, .NET 2.0
\par > class library or desktop app project(winform or console) do use a new
\par > AppSettings class to store and retrieve such configuration info (like
\par > webservice url string , connection string....). However, if we dig into
\par > that appsettings class's code, we'll find that will also point to the
\par > application configuration file (app.config ) underlyingly. So for your
\par > scenario, when you add a web reference in class library project, you'll
\par > find that the class library will add a app.config file in it which has the
\par > entry that store the URL string (if using Dynamic Behavior). So when we
\par > deploy the class library assembly(add referece to it ) in target client
\par > application(winform, asp.net ,or console...), we can just override (or just
\par > copy) the setting in our class library project's app.config to the target
\par > application 's application config file (app.config or web.config...)
\par >
\par > Hope this helps. Thanks,
\par >
\par > Steven Cheng
\par > Microsoft Online Support
\par >
\par > Get Secure! www.microsoft.com/security
\par > (This posting is provided "AS IS", with no warranties, and confers no
\par > rights.)
\par >
\par >
\par >
\par >
\par >
\par > --------------------
\par > Thread-Topic: Dynamic URL Behavior & Configuration
\par > thread-index: AcYiBL/X/vTGsN4ITVe0D7o2pLoP6A==
\par > X-WBNR-Posting-Host: 209.77.204.49
\par > From: "=?Utf-8?B?TWlrZSBMaXZlbnNwYXJnYXI=?=" <wally417@xxxxxxxxxxxxxxxxx>
\par > Subject: Dynamic URL Behavior & Configuration
\par > Date: Wed, 25 Jan 2006 15:12:02 -0800
\par > Lines: 28
\par > Message-ID: <193269E2-57C3-44F2-BC55-23C75CDE783A@xxxxxxxxxxxxx>
\par > MIME-Version: 1.0
\par > Content-Type: text/plain;
\par > \tab charset="Utf-8"
\par > Content-Transfer-Encoding: 7bit
\par > X-Newsreader: Microsoft CDO for Windows 2000
\par > Content-Class: urn:content-classes:message
\par > Importance: normal
\par > Priority: normal
\par > X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
\par > Newsgroups: microsoft.public.dotnet.framework.webservices
\par > NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
\par > Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
\par > Xref: TK2MSFTNGXA02.phx.gbl
\par > microsoft.public.dotnet.framework.webservices:13472
\par > X-Tomcat-NG: microsoft.public.dotnet.framework.webservices
\par >
\par > We have an application converted from v1.1 Framework to v2.0. The
\par > executable
\par > references a class library which in turn has a web reference. The web
\par > reference 'URL Behavior' is set to dynamic. We added an entry to the
\par > executable's .exe.config file to specify the URL, and under the 1.1
\par > framework
\par > this worked well. Unfortunately, this is not working under the 2.0
\par > framework.
\par >
\par > I see in the Reference.cs file under the web service reference the
\par > following
\par > code:
\par >
\par > this.Url =
\par > global::ClassLibraryName.Properties.Settings.Default.WebServiceName
\par >
\par > and I see in Settings.settings in the class library an entry for the web
\par > service. Applications deployed under v2.0 are indeed using the URL
\par > specified
\par > in Settings.settings.
\par >
\par > It looks to me as if the web reference is no longer using the exe.config
\par > file to pick up the url for the web service, and it is not clear to me what
\par > file needs to be modified when the application is deployed to specify the
\par > location of the URL for that deployment.
\par >
\par > How should web references be configured to allow dynamic specification of
\par > their URL, and which deployed files need to be altered to specify the URL?
\par >
\par > Thank you,
\par > Mike
\par >
\par >
\par >
\par >
\par \pard
\par
\par }