I've been asking dumb questions lately, so why stop now?
I'm wondering if it is possible to use Web Services without the XML
Serialization which requires parameterless constructors and public fields.
I guess there are two easy ways to satisfy this requirement.  Either there

We have a web application written in asp.net (1.1).  I'm not going to go
into too much detail but we use a DLL to communicate with the database and
also a couple of webservices.  When we deployed version 1, everything
deployed OK on our webserver.  We deployed the application and ...

I'm working on migrating a webservice my company currently has written in
PHP over to a .Net webservice. Our service works like this:
Applications makes a HTTP POST request to the webservice with the raw post
data consisting of XML.

My app is a general purposes app and not a specific one.
This means that customer who bought the application can have a web service
placed on the server on any given URL.
I use the wsdl tool to create the service class, but the reference to the

I need to create a webserivce which is able to talk to the following
components:
1) Another webservice which is written by java and talks to its own backend
database to authenticate the users