Re: Big-Picture Question (Web Services, RegNow)



Hi Laurent,

Additionally, classes (or arrays) are easy to handle in SOAP, so as long
as your properties are simple types, it's really OK to "pack" them.

If it's really not an issue, do you have any idea why the VS environment
does not support it for testing?

Thanks for your additional comments. I've printed them out and will go
through them in more detail later.

Thanks again!

Jumping ahead, the next items I'm wondering about have to do with
deployment of the service. Although I'm somewhat mystified that the
default is to deploy Web pages uncompiled, my understanding is that they
can be precompiled. So there are a few issues I'm starting to wonder
about. Any input you might have would be appreciated.

1. How can I precompile a Web service before placing it on the Web.

When you use the VS2005 website model, you can publish your web service
just like you publish a website, by using the menu "Build / Publish". It's
the same process, exactly.

However, I recommend you to switch to the Web Application Projet, which is
an add-on to Visual Studio and which allows you to develop your websites
like you did in VS2003, with total control on the DLL.

http://webproject.scottgu.com/

After installing, choose "New project", and then "Web" and then "ASP.NET
Web Service Application".

2. What does a Web service compile to, and when would something like this
be compiled to a DLL rather than other types of pages?

A web service is made of a front-end file (.ASMX), which is the entry
point, and code-behind (C#). The compilation model is exactly the same as
for ASPX pages: The code behind gets compiled in the DLL, additional
referenced DLLs get copied too, and the ASMX file remains as a text file.

3. And where would I typically upload the compiled file to (which
folder).

You don't have a choice: Except by tweaking the configuration (which I
wouldn't), the DLLs must be placed in the "bin" folder under the root of
your virtual folder.

Try publishing your web service to a local folder, and then you'll see
that the folders are created, and the files copied.

Thanks!

HTH,
Laurent
--
Laurent Bugnion, GalaSoft
Software engineering: http://www.galasoft-LB.ch
Private/Malaysia: http://mypage.bluewin.ch/lbugnion
Support children in Calcutta: http://www.calcutta-espoir.ch

--
Jonathan Wood
SoftCircuits Programming
http://www.softcircuits.com


.



Relevant Pages

  • Re: ASP .NET 2.0 Visual Studio 2005 - deploying - no DLLs
    ... and source siles in the App_Code folder) is on ... I thought that the application would be compiled on the server the first ... and this would create the DLL files in the BIN folder. ... triggered a compilation of the website, but there are no DLL files in the ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: security - web service - vb.net - Help....
    ... There are 2 projects - a web service and a vb.net dll. ... The dll might also be used by a stand-alone vb .exe or asp.net pages. ... form button_click event and the folder was copied successfully by the dll. ... >> If I type the command in a command window it executes successfully - ...
    (microsoft.public.dotnet.security)
  • Re: about codebehind..
    ... > one dll. ... You will then get one dynamic assembly compiled for the folder in which the ... Second Scenario: Non-Batch Compilation ... The assemblies that get ...
    (microsoft.public.dotnet.framework.aspnet)
  • Security issue or not on windows 2003 server.
    ... I have a web service, which in turn uses a dll that is installed on the ... The dll is deployed to the GAC. ... This works when it run the web service on windows 2000 server, ... I tried sharing the folder as well. ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: Big-Picture Question (Web Services, RegNow)
    ... That said, SOAP is an acknowledged standard now, and more and more platforms will support it. ... When you use the VS2005 website model, you can publish your web service just like you publish a website, by using the menu "Build / Publish". ... However, I recommend you to switch to the Web Application Projet, which is an add-on to Visual Studio and which allows you to develop your websites like you did in VS2003, with total control on the DLL. ... the DLLs must be placed in the "bin" folder under the root of your virtual folder. ...
    (microsoft.public.dotnet.framework.aspnet)