Policy files will still work fine .. I'm doing it now in across multiple
SOAP tcp services. IMHO it is better practice to use WS-Policy if possible
since it is easier to maintain for someone unfamiliar with your project.
Alex
Alex,
Thanks a lot for your reply. However I ran into a problem. I used to have a
solution with two projects: one project for my client win app and another
project for my web service. Since I decided to use SOAP tcp service I
replaced my previous Web project with a normal C# project (similar to WSE
sample). This in turn led me to one only app.config file (in my client
project). I double-checked MSDN which confirmed that in such a situation I
can only have one app.config file. Now the problem: how do I specify my
server-side policy? I created policy.config for the server project but where
do I reference it? It used to be in the web.config. My one and only
app.config includes an entry for the client-side policy.config. What am I
supposed to do with the server side policy?
Thanks in advance.
Anna
> Policy files will still work fine .. I'm doing it now in across multiple
> SOAP tcp services. IMHO it is better practice to use WS-Policy if possible
[quoted text clipped - 10 lines]
> > Thanks in advance.
> > Anna
Alex Trebek - 04 Aug 2005 14:49 GMT
Anna,
You need to refer to your policy config in the app.config via the
<microsoft.web.services2>
<policy>
<!-- Path your config -->
<cache name="../../policyCache.config" />
</policy>
I usually do this from the VS IDE by right-clicking the project file in the
solution explorer and choosing 'WSE 2.0 Settings'. This will handle the
mapping of the app.config to the policy.config. If you do this, you still
have only one true config for the project but your settings persist in the
policy.config file as a part of the project. This also applies for web
projects as well.
HTH,
Alex
> Alex,
>
[quoted text clipped - 32 lines]
>> > Thanks in advance.
>> > Anna