We did a same code base test between 1.1 and 3.5.
In 1.1, when your .NET application reference a library with web reference
(dynamic), you can always easily overwrite the default URL by specifying a
different URL in your app config file or web config file.
Now, in 3.5, I find that this no longer works. No matter what URL you
specify in app config, it still point to default URL, which seems to be a
serious bug to us.
I am not sure if this is an intentional change, (not find any clue yet) or a
bug.
I cannot use new WCF for this, as the web service we are referencing is a
web service written in Java.
Any insight?
Thanks
In 1.1, when your .NET application reference a library with web reference
(dynamic), you can always easily overwrite the default URL by specifying a
different URL in your app config file or web config file.
Now, in 3.5, I find that this no longer works. No matter what URL you
specify in app config, it still point to default URL, which seems to be a
serious bug to us.
I am not sure if this is an intentional change, (not find any clue yet) or a
bug.
I cannot use new WCF for this, as the web service we are referencing is a
web service written in Java.
Any insight?
Thanks
Comment