>Dangerous depends on whether your server gets compromised <g>...
>
>Yeah, I wouldn't recommend that route really, but it's by far the easiest deployment model at this point and in some situations this may be Ok.

On a test server, I have uploaded the asmx and the DLL in the bin directory under. That's it. I was able to make the Web Service work. However, as we mentioned, it is the process of building the compile which is a little bit different. First of all, we cannot indicate in the publisher to use a sub directory of the project directory. We have to use another branch level. Then, it copies everything under that directory. The only think I need is the DLL. IAC, this only applies to Web Services and I don't compile that much as this is tested locally before and when it works, we deploy.

>I can't argue with that and I've complained bitterly about this since I originally saw it.
>
>There's a tool that you can install - Web Deployment Projects - that gets you close to the 2003 behavior. More info here:
>
>http://west-wind.com/weblog/posts/3475.aspx
>
>You can follow the links from there to download and find out more about it.

Thanks for the reference