Hi All, I have a doubt on WS. Initial deployment of an asp.net app which
calls a websvc includes copying all the webreferences and proxy files
(including the .cs files of the proxy)
If I build a new version of the asp.net app and don't change anything in the
underlying WS or the way it calls it, do I have to copy over all the
webreferences again to the production box? or I can just copy the .dll file
of asp.net app in the bin? (if no aspx pages has changed)

"Vai2000" <no****@microsoft.com> wrote in message
news:Ox*************@TK2MSFTNGP15.phx.gbl...

Hi All, I have a doubt on WS. Initial deployment of an asp.net app which calls a websvc includes copying all the webreferences and proxy files (including the .cs files of the proxy) If I build a new version of the asp.net app and don't change anything in the underlying WS or the way it calls it, do I have to copy over all the webreferences again to the production box? or I can just copy the .dll file of asp.net app in the bin? (if no aspx pages has changed)

Hi All, I have a doubt on WS. Initial deployment of an asp.net app which calls a websvc includes copying all the webreferences and proxy files (including the .cs files of the proxy)
You can simply copy the .asmx files, the web.config, and the dll's in the
/bin directory. You do not need to copy the .cs files.
If I build a new version of the asp.net app and don't change anything in the underlying WS or the way it calls it, do I have to copy over all the webreferences again to the production box?
You do not have to copy the web service files again.
or I can just copy the .dll file of asp.net app in the bin? (if no aspx pages has changed)
It is a good idea to copy the aspx files if the version of the dll under the
aspx files changes. This is a "best practice" for configuration management.
However, there's no technical requirement if you believe that you didn't
make a mistake.

Note that the URL of the web service that you refer to in development may be
a different URL than the one you want to use in production. You can change
this in code (there are a couple of examples online for changing this by
simply looking up a new value and assigning it to the URL property of the
web service proxy object), or you can have the framework do it for you by
changing the URL Behavior property from Static to Dynamic, which allows the
framework to generate the code for you to look up the URL.

Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
"Vai2000" <no****@microsoft.com> wrote in message
news:Ox*************@TK2MSFTNGP15.phx.gbl... Hi All, I have a doubt on WS. Initial deployment of an asp.net app which calls a websvc includes copying all the webreferences and proxy files (including the .cs files of the proxy) If I build a new version of the asp.net app and don't change anything in the underlying WS or the way it calls it, do I have to copy over all the webreferences again to the production box? or I can just copy the .dll file of asp.net app in the bin? (if no aspx pages has changed)

Thanks for all the feedback. Yes I have configured by WS to be dynamic and
inside the proxy .cs file I already use the property value from the config.
at Run Time. I am asking this question since recently we are experiencing
Timeout problem in calling the WebServices from the client.
"Underlying connection closed Request is canceled"
We did updated the ASPX Application and didn't changed anything to the
WebReferences as nothing was changed in the WS. reference in the code.

1 Last doubt so which files from the WebReference folder should be deployed
along with an ASPX App if that app is calling a WS?

Hi All, I have a doubt on WS. Initial deployment of an asp.net app which calls a websvc includes copying all the webreferences and proxy files (including the .cs files of the proxy) You can simply copy the .asmx files, the web.config, and the dll's in the /bin directory. You do not need to copy the .cs files.

If I build a new version of the asp.net app and don't change anything in the underlying WS or the way it calls it, do I have to copy over all the webreferences again to the production box?

You do not have to copy the web service files again.

or I can just copy the .dll file of asp.net app in the bin? (if no aspx pages has changed)

It is a good idea to copy the aspx files if the version of the dll under

the aspx files changes. This is a "best practice" for configuration
management. However, there's no technical requirement if you believe that you didn't make a mistake.

Note that the URL of the web service that you refer to in development may
be a different URL than the one you want to use in production. You can
change this in code (there are a couple of examples online for changing this by simply looking up a new value and assigning it to the URL property of the web service proxy object), or you can have the framework do it for you by changing the URL Behavior property from Static to Dynamic, which allows
the framework to generate the code for you to look up the URL.

Disclaimer: Opinions expressed in this forum are my own, and not representative of my employer. I do not answer questions on behalf of my employer. I'm just a programmer helping programmers. -- "Vai2000" <no****@microsoft.com> wrote in message news:Ox*************@TK2MSFTNGP15.phx.gbl...

Hi All, I have a doubt on WS. Initial deployment of an asp.net app which calls a websvc includes copying all the webreferences and proxy files (including the .cs files of the proxy) If I build a new version of the asp.net app and don't change anything in the underlying WS or the way it calls it, do I have to copy over all the webreferences again to the production box? or I can just copy the .dll file of asp.net app in the bin? (if no aspx pages has changed)

updating a web service is an interesting issue in debugging due to ASP.Net
caching. Make sure to update the web.config, or refresh the app pool,
between updating the pages and testing the app. Otherwise, you may change
the code, and not see the change!

which files from the WebReference folder should be deployed along with an ASPX App if that app is calling a WS?
none of them. this folder is used by Visual Studio, not ASP.Net. VS uses
these files to create code. That code is compiled into your dll.

Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
"Vai2000" <no****@microsoft.com> wrote in message
news:us**************@tk2msftngp13.phx.gbl... Thanks for all the feedback. Yes I have configured by WS to be dynamic and inside the proxy .cs file I already use the property value from the config. at Run Time. I am asking this question since recently we are experiencing Timeout problem in calling the WebServices from the client. "Underlying connection closed Request is canceled" We did updated the ASPX Application and didn't changed anything to the WebReferences as nothing was changed in the WS. reference in the code.

1 Last doubt so which files from the WebReference folder should be deployed along with an ASPX App if that app is calling a WS?

> Hi All, I have a doubt on WS. Initial deployment of an asp.net app > which > calls a websvc includes copying all the webreferences and proxy files > (including the .cs files of the proxy)

You can simply copy the .asmx files, the web.config, and the dll's in the /bin directory. You do not need to copy the .cs files.

> If I build a new version of the asp.net app and don't change anything > in > the > underlying WS or the way it calls it, do I have to copy over all the > webreferences again to the production box?

You do not have to copy the web service files again.

> or I can just copy the .dll file > of asp.net app in the bin? (if no aspx pages has changed)

It is a good idea to copy the aspx files if the version of the dll under

the

aspx files changes. This is a "best practice" for configuration

management.

However, there's no technical requirement if you believe that you didn't make a mistake.

Note that the URL of the web service that you refer to in development may

be

a different URL than the one you want to use in production. You can

change

this in code (there are a couple of examples online for changing this by simply looking up a new value and assigning it to the URL property of the web service proxy object), or you can have the framework do it for you by changing the URL Behavior property from Static to Dynamic, which allows

Disclaimer: Opinions expressed in this forum are my own, and not representative of my employer. I do not answer questions on behalf of my employer. I'm just a programmer helping programmers. -- "Vai2000" <no****@microsoft.com> wrote in message news:Ox*************@TK2MSFTNGP15.phx.gbl...

> Hi All, I have a doubt on WS. Initial deployment of an asp.net app > which > calls a websvc includes copying all the webreferences and proxy files > (including the .cs files of the proxy) > If I build a new version of the asp.net app and don't change anything > in > the > underlying WS or the way it calls it, do I have to copy over all the > webreferences again to the production box? or I can just copy the .dll > file > of asp.net app in the bin? (if no aspx pages has changed) > > TIA > >