Deploying .Net Web Service

[Bryan Dickerson]

I fairly have my Web Service working the way that I want, so my next step
will be to deploy it on a server. Do I just add a deployment/install
project, build it and install it on the server?

TIA!

 

[m.posseth]

well i just create a release build with the precompile option on ( as i do
not want my sourcecode files on the deploy server ) and copy this complete
subdirectory to the virtual path on my webserver

regards

Michel Posseth [MCP]

 

[Bryan Dickerson]

I'm using VS 2003. Does/Should the "Click-Once" thing work for me or is
that only in 2005?

well i just create a release build with the precompile option on ( as i
do not want my sourcecode files on the deploy server ) and copy this
complete subdirectory to the virtual path on my webserver

regards

Michel Posseth [MCP]

 

[Bryan Dickerson]

Does anyone else do this any differently? Just curious...

well i just create a release build with the precompile option on ( as i
do not want my sourcecode files on the deploy server ) and copy this
complete subdirectory to the virtual path on my webserver

regards

Michel Posseth [MCP]

 

[m.posseth]

Well with VS 2003 we just build the project in release mode and copy it to
the webserver , with VS.Net 2005 you have some more options ( precompile or
not )

click once is ment for deploying your apps to end users afaik

deploying a web project is verry easy as it is all XCOPY ware ( drag and
drop in a virtual directory and it should work, you may also use the copy
option in your project IDE to deploy the app )

regards

Michel Posseth

I'm using VS 2003. Does/Should the "Click-Once" thing work for me or is
that only in 2005?

well i just create a release build with the precompile option on ( as i
do not want my sourcecode files on the deploy server ) and copy this
complete subdirectory to the virtual path on my webserver

regards

Michel Posseth [MCP]

I fairly have my Web Service working the way that I want, so my next step
will be to deploy it on a server. Do I just add a deployment/install
project, build it and install it on the server?

TIA!

 

[Bryan Dickerson]

Thanks for your response, but I'm not quite clear on what to drag and where
to drop it. And where is this copy option in the IDE?

Well with VS 2003 we just build the project in release mode and copy it
to the webserver , with VS.Net 2005 you have some more options (
precompile or not )

click once is ment for deploying your apps to end users afaik

deploying a web project is verry easy as it is all XCOPY ware ( drag and
drop in a virtual directory and it should work, you may also use the copy
option in your project IDE to deploy the app )

regards

Michel Posseth

I'm using VS 2003. Does/Should the "Click-Once" thing work for me or is
that only in 2005?

well i just create a release build with the precompile option on ( as i
do not want my sourcecode files on the deploy server ) and copy this
complete subdirectory to the virtual path on my webserver

regards

Michel Posseth [MCP]



I fairly have my Web Service working the way that I want, so my next
step will be to deploy it on a server. Do I just add a
deployment/install project, build it and install it on the server?

TIA!

 

[m.posseth]

Hello Bryan

here is some more good info

http://msdn.microsoft.com/library/d...de/html/cpconaspnetapplicationwalkthrough.asp

http://samples.gotdotnet.com/quickstart/aspplus/doc/deployment.aspx

if you have anny more questions or need some more guidance after reading
this please feel free to ask

regards

Michel Posseth [MCP]

Thanks for your response, but I'm not quite clear on what to drag and
where to drop it. And where is this copy option in the IDE?

Well with VS 2003 we just build the project in release mode and copy it
to the webserver , with VS.Net 2005 you have some more options (
precompile or not )

click once is ment for deploying your apps to end users afaik

deploying a web project is verry easy as it is all XCOPY ware ( drag and
drop in a virtual directory and it should work, you may also use the copy
option in your project IDE to deploy the app )

regards

Michel Posseth

I'm using VS 2003. Does/Should the "Click-Once" thing work for me or is
that only in 2005?


well i just create a release build with the precompile option on ( as
i do not want my sourcecode files on the deploy server ) and copy this
complete subdirectory to the virtual path on my webserver

regards

Michel Posseth [MCP]



I fairly have my Web Service working the way that I want, so my next
step will be to deploy it on a server. Do I just add a
deployment/install project, build it and install it on the server?

TIA!

 

[Bryan Dickerson]

Thanks for your help and responses. I now have a barrage of questions:
The main idea is that my WebService modules are in
"c:\inetpub\wwwroot\WSMyService", so I will need to copy that directory and
everything underneath to the equivalent IIS wwwroot directory on the server
and it should 'magically' work, right?
I guess I should also make sure the proper version of the .Net Framework is
loaded on the server, right? I'm using VS 2003, so I guess I'm using Fx
1.1; how would I verify that?
Are there any IIS things that need to be done on the server box? (This is a
private web service)
Also is there a way, without the benefit of having VS 2003 loaded on the
server, to test the web service? Copy a build of my test program and the
test input files and run them?

Hello Bryan

here is some more good info

http://msdn.microsoft.com/library/d...de/html/cpconaspnetapplicationwalkthrough.asp

http://samples.gotdotnet.com/quickstart/aspplus/doc/deployment.aspx

if you have anny more questions or need some more guidance after reading
this please feel free to ask

regards

Michel Posseth [MCP]

Thanks for your response, but I'm not quite clear on what to drag and
where to drop it. And where is this copy option in the IDE?

Well with VS 2003 we just build the project in release mode and copy
it to the webserver , with VS.Net 2005 you have some more options (
precompile or not )

click once is ment for deploying your apps to end users afaik

deploying a web project is verry easy as it is all XCOPY ware ( drag
and drop in a virtual directory and it should work, you may also use the
copy option in your project IDE to deploy the app )

regards

Michel Posseth



I'm using VS 2003. Does/Should the "Click-Once" thing work for me or
is that only in 2005?


well i just create a release build with the precompile option on ( as
i do not want my sourcecode files on the deploy server ) and copy
this complete subdirectory to the virtual path on my webserver

regards

Michel Posseth [MCP]



I fairly have my Web Service working the way that I want, so my next
step will be to deploy it on a server. Do I just add a
deployment/install project, build it and install it on the server?

TIA!

 

[m.posseth]

sorry for the late reaction ... ( missed this thread in my group reader )

"c:\inetpub\wwwroot\WSMyService", so I will need to copy that directory and

everything underneath to the equivalent IIS wwwroot directory on the
server and it should 'magically' work, right?

this is a definite Yes ....( it should work like that )

I guess I should also make sure the proper version of the .Net Framework
is loaded on the server, right? I'm using VS 2003, so I guess I'm using
Fx 1.1; how would I verify that?

for VS .Net 2003 applications to work on IIS you must have the Framework
1.1 or newer installed

Also is there a way, without the benefit of having VS 2003 loaded on the
server, to test the web service? Copy a build of my test program and the
test input files and run them?

Yes this is possible with this tag in your webconfig file
<add name="Documentation"/>



see one of my services http://online.autotools.nl/ATWebService/Service.asmx

and try the fblnCarHasAutotools method ( VAG , 224 for instance )

and you will see the typical response of this service only test services
lime this that use simple datatypes and return simple datatypes ( see the 2
other methods . they do not show the form interface as they expect
datasets )





so it looks like this
<webServices>

<protocols>

<add name="HttpSoap"/>

<add name="HttpPost"/>

<add name="HttpGet"/>

<add name="HttpPostLocalhost"/>

<!-- Documentation enables the documentation/test pages -->

<add name="Documentation"/>

</protocols>

</webServices>

regards

Michel Posseth [MCP]

Thanks for your help and responses. I now have a barrage of questions:
The main idea is that my WebService modules are in
"c:\inetpub\wwwroot\WSMyService", so I will need to copy that directory
and everything underneath to the equivalent IIS wwwroot directory on the
server and it should 'magically' work, right?
I guess I should also make sure the proper version of the .Net Framework
is loaded on the server, right? I'm using VS 2003, so I guess I'm using
Fx 1.1; how would I verify that?
Are there any IIS things that need to be done on the server box? (This is
a private web service)
Also is there a way, without the benefit of having VS 2003 loaded on the
server, to test the web service? Copy a build of my test program and the
test input files and run them?

Hello Bryan

here is some more good info

http://msdn.microsoft.com/library/d...de/html/cpconaspnetapplicationwalkthrough.asp

http://samples.gotdotnet.com/quickstart/aspplus/doc/deployment.aspx

if you have anny more questions or need some more guidance after reading
this please feel free to ask

regards

Michel Posseth [MCP]

Thanks for your response, but I'm not quite clear on what to drag and
where to drop it. And where is this copy option in the IDE?


Well with VS 2003 we just build the project in release mode and copy
it to the webserver , with VS.Net 2005 you have some more options (
precompile or not )

click once is ment for deploying your apps to end users afaik

deploying a web project is verry easy as it is all XCOPY ware ( drag
and drop in a virtual directory and it should work, you may also use
the copy option in your project IDE to deploy the app )

regards

Michel Posseth



I'm using VS 2003. Does/Should the "Click-Once" thing work for me or
is that only in 2005?


well i just create a release build with the precompile option on (
as i do not want my sourcecode files on the deploy server ) and copy
this complete subdirectory to the virtual path on my webserver

regards

Michel Posseth [MCP]



I fairly have my Web Service working the way that I want, so my next
step will be to deploy it on a server. Do I just add a
deployment/install project, build it and install it on the server?

TIA!

 

[Bryan Dickerson]

Thanks for your help. But I'm unclear on what you mean about testing it
with the "<add name="Documentation"/> in the Web.config file. Can you
elaborate?

Thanx again!

sorry for the late reaction ... ( missed this thread in my group reader )

"c:\inetpub\wwwroot\WSMyService", so I will need to copy that directory
and

everything underneath to the equivalent IIS wwwroot directory on the
server and it should 'magically' work, right?

this is a definite Yes ....( it should work like that )

I guess I should also make sure the proper version of the .Net Framework
is loaded on the server, right? I'm using VS 2003, so I guess I'm using
Fx 1.1; how would I verify that?

for VS .Net 2003 applications to work on IIS you must have the Framework
1.1 or newer installed

Also is there a way, without the benefit of having VS 2003 loaded on the
server, to test the web service? Copy a build of my test program and the
test input files and run them?

Yes this is possible with this tag in your webconfig file
<add name="Documentation"/>



see one of my services
http://online.autotools.nl/ATWebService/Service.asmx

and try the fblnCarHasAutotools method ( VAG , 224 for instance )

and you will see the typical response of this service only test services
lime this that use simple datatypes and return simple datatypes ( see the
2 other methods . they do not show the form interface as they expect
datasets )





so it looks like this
<webServices>

<protocols>

<add name="HttpSoap"/>

<add name="HttpPost"/>

<add name="HttpGet"/>

<add name="HttpPostLocalhost"/>

<!-- Documentation enables the documentation/test pages -->

<add name="Documentation"/>

</protocols>

</webServices>

regards

Michel Posseth [MCP]

Thanks for your help and responses. I now have a barrage of questions:
The main idea is that my WebService modules are in
"c:\inetpub\wwwroot\WSMyService", so I will need to copy that directory
and everything underneath to the equivalent IIS wwwroot directory on the
server and it should 'magically' work, right?
I guess I should also make sure the proper version of the .Net Framework
is loaded on the server, right? I'm using VS 2003, so I guess I'm using
Fx 1.1; how would I verify that?
Are there any IIS things that need to be done on the server box? (This is
a private web service)
Also is there a way, without the benefit of having VS 2003 loaded on the
server, to test the web service? Copy a build of my test program and the
test input files and run them?

Hello Bryan

here is some more good info

http://msdn.microsoft.com/library/d...de/html/cpconaspnetapplicationwalkthrough.asp

http://samples.gotdotnet.com/quickstart/aspplus/doc/deployment.aspx

if you have anny more questions or need some more guidance after reading
this please feel free to ask

regards

Michel Posseth [MCP]


Thanks for your response, but I'm not quite clear on what to drag and
where to drop it. And where is this copy option in the IDE?


Well with VS 2003 we just build the project in release mode and copy
it to the webserver , with VS.Net 2005 you have some more options (
precompile or not )

click once is ment for deploying your apps to end users afaik

deploying a web project is verry easy as it is all XCOPY ware ( drag
and drop in a virtual directory and it should work, you may also use
the copy option in your project IDE to deploy the app )

regards

Michel Posseth



I'm using VS 2003. Does/Should the "Click-Once" thing work for me or
is that only in 2005?


well i just create a release build with the precompile option on
( as i do not want my sourcecode files on the deploy server ) and
copy this complete subdirectory to the virtual path on my webserver

regards

Michel Posseth [MCP]



I fairly have my Web Service working the way that I want, so my next
step will be to deploy it on a server. Do I just add a
deployment/install project, build it and install it on the server?

TIA!

 

[Bryan Dickerson]

Disregard the previous message! I just didn't read far enough! I'll post
back if I have any other questions.

Thanks for your help. But I'm unclear on what you mean about testing it
with the "<add name="Documentation"/> in the Web.config file. Can you
elaborate?

Thanx again!

sorry for the late reaction ... ( missed this thread in my group reader )

"c:\inetpub\wwwroot\WSMyService", so I will need to copy that directory
and

everything underneath to the equivalent IIS wwwroot directory on the
server and it should 'magically' work, right?

this is a definite Yes ....( it should work like that )

I guess I should also make sure the proper version of the .Net Framework
is loaded on the server, right? I'm using VS 2003, so I guess I'm using
Fx 1.1; how would I verify that?

for VS .Net 2003 applications to work on IIS you must have the Framework
1.1 or newer installed

Also is there a way, without the benefit of having VS 2003 loaded on the
server, to test the web service? Copy a build of my test program and
the test input files and run them?

Yes this is possible with this tag in your webconfig file
<add name="Documentation"/>



see one of my services
http://online.autotools.nl/ATWebService/Service.asmx

and try the fblnCarHasAutotools method ( VAG , 224 for instance )

and you will see the typical response of this service only test services
lime this that use simple datatypes and return simple datatypes ( see the
2 other methods . they do not show the form interface as they expect
datasets )





so it looks like this
<webServices>

<protocols>

<add name="HttpSoap"/>

<add name="HttpPost"/>

<add name="HttpGet"/>

<add name="HttpPostLocalhost"/>

<!-- Documentation enables the documentation/test pages -->

<add name="Documentation"/>

</protocols>

</webServices>

regards

Michel Posseth [MCP]

Thanks for your help and responses. I now have a barrage of questions:
The main idea is that my WebService modules are in
"c:\inetpub\wwwroot\WSMyService", so I will need to copy that directory
and everything underneath to the equivalent IIS wwwroot directory on the
server and it should 'magically' work, right?
I guess I should also make sure the proper version of the .Net Framework
is loaded on the server, right? I'm using VS 2003, so I guess I'm using
Fx 1.1; how would I verify that?
Are there any IIS things that need to be done on the server box? (This
is a private web service)
Also is there a way, without the benefit of having VS 2003 loaded on the
server, to test the web service? Copy a build of my test program and
the test input files and run them?


Hello Bryan

here is some more good info

http://msdn.microsoft.com/library/d...de/html/cpconaspnetapplicationwalkthrough.asp

http://samples.gotdotnet.com/quickstart/aspplus/doc/deployment.aspx

if you have anny more questions or need some more guidance after
reading this please feel free to ask

regards

Michel Posseth [MCP]


Thanks for your response, but I'm not quite clear on what to drag and
where to drop it. And where is this copy option in the IDE?


Well with VS 2003 we just build the project in release mode and
copy it to the webserver , with VS.Net 2005 you have some more
options ( precompile or not )

click once is ment for deploying your apps to end users afaik

deploying a web project is verry easy as it is all XCOPY ware ( drag
and drop in a virtual directory and it should work, you may also use
the copy option in your project IDE to deploy the app )

regards

Michel Posseth



I'm using VS 2003. Does/Should the "Click-Once" thing work for me
or is that only in 2005?


well i just create a release build with the precompile option on
( as i do not want my sourcecode files on the deploy server ) and
copy this complete subdirectory to the virtual path on my webserver

regards

Michel Posseth [MCP]



I fairly have my Web Service working the way that I want, so my
next step will be to deploy it on a server. Do I just add a
deployment/install project, build it and install it on the server?

TIA!