>>
>>I was ask to do some testing on a key level of this company's ASP.Net application. Ok, no problem. They tell me they need to install the applicaion on my machine. Ok, no problem, again. They tell it is a quick install and configuration. They also tell me thet it will only take a few days. DAYS???. Well thet was over two weeks ago. I am still waiting. And they are still trying. They have installed, uninstalled, reinstalled, reformatted my hard drive, installed, configurered, reconfigured. Boy, I love .Net. It have freed up so much time for me. I sure am glad I get paid for all this. Go Microsoft, Go .NET.
>>
>>Wait, they are back again....
>
>They must be doing something wrong <g>.
>
>As long as your web server is up and running, I've found deploying a .NET web app (or web service) to be trivial. Microsoft says, "XCOPY deployment" and I'd agree. If the components are installed in the GAC, it's a little more complicated (but it only takes maybe 10 minutes to builds a simple install for that). If you've got COM components, well, then you're back to normal registration & permission issues.
>
>The one place where they got things right was in web development (that isn't to suggest that I think they got things wrong everywhere else; from what I've seen, it's a mixed bag).

It is not .NET, but all the other applications that our application works with (SQL Server, BizTalk, Scheduled Tasks, IIS, etc.) They are having problems with the permissions between all these applications and servers. The application is a n-tier layout. As the tester for the platform, I need special permissions to verify that the application is doing what the specification says they should do, or not do. This added a level complexity that was not thought of when the application was being built. The degree of added features to the web.config and other .config files is mainly were the problem lies. Personally, I think ASP.Net is a superior environment to the old ASP 3.0. But they have created a monster out of it, which is why it has become difficult to deploy under unique conditions, like mine.

I only related my story more for the humor then to down .NET. :)