Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
If MS Access why not VFP?
Message
From
04/02/2011 12:19:11
 
General information
Forum:
Visual FoxPro
Category:
Visual FoxPro and .NET
Environment versions
Visual FoxPro:
VFP 9 SP2
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01498550
Message ID:
01498786
Views:
71
>>What C# tools are you using regularly? I am always interested in those.

Bonnie's blog gave me lots of data access classes and methods that I have tweaked and use constantly. Too many to enumerate here.

Another tool I use daily is a SQL stored procedure generator Naomi pointed me to. BIG time saver and grief eliminator.

Another that has been a big home run is a PDF merge utility (PDFUtils) I found that allows you to merge pdf's according to whatever rules you need to apply.

Another harnesses a relatively undocumented feature in .NET called FtpWebRequest, which has everything you need to FTP files with good control. Someone on here from Paris (I forget his name) gave me some code that I tweaked a bit and now I have a plug and play FTP tool that uses just .NET components.

Someone did the same thing for email and now I have a simple interface to an email class that uses .NET components

Those are some good ones which come to mind.

Be cautioned tho, tools can bite you. I used a color tabcontrol tool (.NET Winforms don't support colored tab pages) I found and after spending days developing controls and methods depending on it, I discovered an irreparable bug in it and had to scrap all that work.
Moving all those controls and methods to a vanilla tabcontrol was a nightmare.












>Well said, Charles.
>I'm supporting clients on both platforms now and after a couple of years of really struggling with C# I'm finding it increasingly difficult when I have to go back to VFP.
>
>One big deal for me is C#''s intellisense and real time compilation - showing errors and warnings as I type.. With VFP I always had a scratchpad handy to note variable or function names, etc so that I'd remember them when I used them later - no more scratchpads - no more "variable x not found."
>
>
>Another big deal is the plethora of tools (mostly free) that have been developed for the C# platform by 3rd party developers. I'm using them constantly.
>
>I've also come to appreciate the value of strong typing, which was a big pain when I started. I'm finding that my C# apps are more stable over time than my VFP apps, and that I get almost no support calls. I attribute most of that to strong typing which imposes more rigorous demands on me during the development process.
>I spend more time coding, but a lot less time debugging.
>
>From VFP, I miss being able to inherit or copy the methods of a form or a control. That has been a real pain.
>
>It was also nice to be able to put together a simple app that popped out some totals or the like in a few minutes - we call them "handy-dandy's." I can't do anything in fewer than 3 or 4 hours in C# by time I set up the references, connections, blah, blah, etc.
>
>I also miss that wonderful Report Writer. CR is OK, but for me it's nowhere near as easy to use as VFP's.
>
Anyone who does not go overboard- deserves to.
Malcolm Forbes, Sr.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform