>>Craig;
>>
>>I seem to have a communication problem. Our corporation will not allow applications to be written which require additional files on a users machine. It is not my policy and you know how that goes trying to "change city hall"! At this time we have been told "we will not use XP because 80% of our applications will not run on it".
>
>That part I understand.
>
>>
>>I just had this thought that Microsoft had a "vision" that everyone would have Dotnetfx.exe installed and waiting for .NET applications to appear. That may not be required or it may not be the case.
>>
>>I just had the feeling from what I have read that client machines required Dotnetfx.exe to run .NET applications. Running anything created on a development machine has a better chance of working on that machine than on a client machine. :) In our case all apps have to be browser based.
>
>This I don't understand. Having all your apps browser based seems to contradict your above statement about XP, unless you're pushing Java apps down to the client.
>
>Just to clarify...a .Net web app produces standard HTML and sends that to the client. For a pure web-based app the client does not need the framework. Once you start moving to Winforms, which add lots of functionality, you'll need the framework on the client...and eventually that will happen.
>
>For a .Net web app to work, the framework must be installed on the web server.

Craig;

Thank you for the clarification. I see the light and it is good - whoops here comes Doug! :)

Tom