If they want to buy technology (.NET) rather than a solution then you're right- there's really nothing you can do.
.NET, as far as I know, is no magic solution for web apps - you still need to deal with HTML and Javascript. These are common elements that need to be dealt with in any web app.
>Claude,
>
>I may agree with you, but the purpose of this thread (at least as I meant it) was to point that some (many?) IT managers are going dotNET just because it is dotNET. Not because you can or can't do something in VFP, they are not even interested in knowing what can be done with it, if it is a better aproach or whatever! They want dotNET, period! You see what I mean?
>
>OTOH, going web with VFP is not an easy task, because to develop a desktop app all that I need is VFP, to go web I'll need HTML (DHTML), JavaScript etc etc.
>
>Fernando
>
>>Fernando,
>>My point is that I wouldn't bail on VFP for developing a web browser based product/project. It really is not that hard to put one together and re-use your vfp application logic on the web. Doing this would possibly get you new business and allow you to keep using VFP. Using VFP Business Objects that can be called from Web or Desktop makes a lot of sense here if it is possible...
>>
>>>Claude,
>>>
>>>>It's this type of comment and Whil Hentzen's in InfoWeek that are damaging to the perception of Visual FoxPro, in my opinion...
>>>
>>>Think you didn't understand my message: I, BY NO WAYS, am leaving VFP, or *even* thinking about, or promoting this kind of move. You *never* saw me, here or elsewhere, saying that I'd better go C#, you know, to "improve my toolset" etc etc (no offense here to those that say so).
>>>
>>>The opposite! I'm pointing the ABSURD arguments some IT managers are using just to get into the dotNET boat!
>>>
>>>By "Another reason you *should* to go dotNET" I sarcastically "added" another "reason" to justify the move to dotNET.
>>>
>>>What I really wanted, is not arguments to argue with those people, they already have their minds made, I wanted facts to put in front of them, comming from Microsoft (like the excelent work Ken is doing with his monthly letter). Nothing else will change that reallity.
>>>
>>>IT managers are bombed with the dotNET hipe and think they *must* get to it, many don't even know why, but they "know" they should do.
>>>
>>>>vfp can continue to be used as web applications and be accessed by a web browser alone.
>>>
>>>So all apps should go web? There is no place for desktop apps anymore? If that's true, there will be no place for VFP apps in near future (2-3 years), because VFP strength is desktop apps, and all dotNET stuff will play much better in the web than VFP.
>>>
>>>Fernando
>>>
>>>>Not sure what you're talking about - vfp can continue to be used as web applications and be accessed by a web browser alone. It's this type of comment and Whil Hentzen's in InfoWeek that are damaging to the perception of VFP, in my opinion...
>>>>>Hi,
>>>>>
>>>>>This morning I had to hear yet another reason why everybody should migrate to dotNET.
>>>>>
>>>>>Deployment.
>>>>>
>>>>>Deployment? Yes! There is a new corporate decision in one of my clients that no software (i.e. applications) should be installed in a user's PC.
>>>>>
>>>>>I argued that *all* my applications don't reside in user's PCs and that there is no install routines whatsoever in order for a user to use *any* of my applications (all .exe reside in specific server's directories, and .ini files and dbfs as well). All that should be done is to create a shortcut in user's PC desktop to start the program and, if that's the case, configure an ODBC connection if the app needs to access an SQL backend. Aha!!! so you *must* install something in a user's PC!
>>>>>
>>>>>I also presented the WTS option. NO! All should be done via "web" access (i.e. using a browser) and *all* apps should be web applications, accessed by and running under a browser, and... it should be developed in dotNET!
>>>>>
>>>>>That's all.
>>>>>
>>>>>Thanks for your time reading this message
>>>>>
>>>>>Fernando