Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Which is best for Desktop Apps VFP?.NET
Message
From
19/12/2003 17:54:59
 
 
To
19/12/2003 17:42:57
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00860600
Message ID:
00860895
Views:
71
Bob:
Another question. It was posted that .Net will require more powerful machines, is this your opinion also?

How would a .Net app run on a Pentuim III machine w/256 RAM?

TIA

Mal

>>Bob:
>>
>>Not sure what to make of your post.
>>I'm, presently, interest in only desktop apps.
>>Does your comment still apply?
>
>Sure it does... as someone said to you, I can do some stuff in VFP in 3 lines of code, that would take 10 or 15 lines of code in .Net (of course VS.Net writes alot of that code for you.)
>
>I just wanted to point out that it balances out with the things you can do in .Net in a few lines of code that would take ALOT of code in VFP. Or, is not even doable in VFP.
>
>One case in point, and this is espesially relevent for Desktop apps is multi-threading. In a .Net app you could have backround processing, for example lets say printing. Your user wouldn't have to wait for a report to process cause it would be done on another thread. You can't do this in VFP at all!
>
>You can use 'zero touch' deployment with .Net windows forms app. The app will look to see if there is a new version of the assembly it needs on the server, and if so, it will download it automatically. Sure, you could do it in VFP, but you would have to code it, .Net builds this in.
>
>In .Net you can write your assemblys against a certain version of code, say your class libraries. Then you can update your class libraries to a new version, install it side-by-side on the machine with the old version, and deploy and app that uses the new version. No dll version hell.
>
>.Net apps run in the CLR sand box, so the user can set permissions on what that app can do, so they don't have to worry about your app deleting critical stuff.
>
>Other than the .Net runtime... your .NEt app doesn't even need to be installed. Just drop it into a folder on the pc, and launch the EXE. All of the settings and meta data are in the .DLL... no registry settings needed. If you do need that stuff an XML (text file) config file is there and you or your user can easily edit it as needed rather than fighting the registry.
>
>HTH,
>BOb
>
>
>>
>>Thanks,
>>
>>Mal
>>
>>>>Terry:
>>>>
>>>>"many, many"?
>>>>
>>>>Didn't know that ... thanks.
>>>
>>>Of course, there are alot of things you can do in .Net with 3 lines of code that you can't even do in VFP!!! (Well, you could with a few hundred lines of code and the Win32 api or a Win32 dll.)
>>>
>>>BOb
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform