Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Services / November 2004

Tip: Looking for answers? Try searching our database.

Change search path.

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Kevin Burton - 02 Nov 2004 20:25 GMT
I have several web services and they all rely on the assemblies in a root
directory. Right now I have something like:

A
 web service B
 web service C
 .

Where 'web service B' is a sub directory of A containing the .asmx files,
the resource files, global asmx, etc. The assemblies that support each of the
web services are currently in A so in order for 'web service B' to find the
assemblies I would need to add something like <probing privatePath=".."> to
web.config in order for the assemblies to be found. The <probing> element
specifically prohibits specifying anything but sub-directories. Any ideas on
how I might solve this problem or restructure my app? Could I point the
virtual directory to say 'web service B' and have the application base be one
directory up (in A)? If so how?

Thank you.

Kevin Burton
Dan Rogers - 15 Nov 2004 23:09 GMT
Hi Kevin,

A few options you have that are pretty simple include copying the DLL's
into the bin directory for each application, or if you want only one copy
of the DLL on the system, place it where you like and add it to the GAC.  
To add to the GAC, the assembly will need to have a strong name, and you
will want to consider whether you want both applications locked around that
DLL.  Once in the GAC, all requests for a particular assembly (not found in
the local directory) will be resolved to the GAC copy.  This means that if
you want to update the DLL, you'll need to implement a versioning policy or
take both applications off line.

Hope this helps,

Dan Rogers
Microsoft Corporation
--------------------
>Thread-Topic: Change search path.
>thread-index: AcTBEaggP3zLNHFdQoCidK5WfpGbRg==
[quoted text clipped - 17 lines]
>Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.dotnet.framework.aspnet.webservices:26352
>X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
>
[quoted text clipped - 19 lines]
>
>Kevin Burton

Rate this thread:







Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.