>> FWIW, I loath Microsoft. We have a client who
>> runs a program that, for the first time, uses .NET.
>> They're used to getting upgrades to address bugs
>> and add features, but they're really disappointed
>> with this upgrade because - surprise, surprise - it
>> now runs slower.
What a shocker. I certainly wasn't expecting an
unbiased opinion on .NET from a VFP programmer 🙂
Basically, it's a fairly common for those who aren't
able to access new technology, to routinely and
opportunistically obliterate it with uneducated and
largely baseless slander.
.NET is a dynamic execution environment, but it isn't
fair to only consider or point out the most obvious
disadvantage, even if you were familiar with all the
advantages that clearly outweigh that. Yes of course,
its slower.
But that's because .NET is designed for the future,
rather than to cater to the limitations of those who
stubbornly choose to remain stuck in the past.
It is designed for a future where some of what it must
now do in software, will eventually be offloaded to
hardware. Your watch; cellphone/pda; toaster oven;
TV; and your car will some day be running what the
CLR eventually evolves into.
The Delphi code that I've ported to .NET runs about
10x slower than it did in native Win32. I was able to
solve most of the issues related to performance by
combining managed code with native code that was
ported to C++.
There's no mandate or requirement that an application
must be written entirely in managed code. The only
requirement is that a developer must be skilled and
able to implement the performance-critical aspects in
native code (e.g., C++).
As far as bugs goes, it's not too terribly uncommon to
find more of them in applications that are migrated
to a new environment and possibly rewritten from the
ground up to leverage what the environment offers.
But, the thing I like the most about .NET, is that it
also seems to have the unintended side-effect of
'shaking out' the imposters and charletans.
That is, people who after having written a couple of
'applications' in VB or some similar 'easy-to-use' tool
like that, fraudulently misrepresent themsleves as
competent, qualified software developers.
If they manage to find some unsuspecting sucker to
hire them and get their foot in the door, what ensues
usually culminates in the form of a mushroom cloud.
I only know that, because of the number of times
I've found myself in the unenviable position of being
tasked with cleaning up the mess.
Regarding your need for a sample, there is sample
code included with the docs.
Assuming you have them, the task is very simple and
basic, to the point where you should be able to figure
it out easily from the docs for the method I pointed
you to in a previous post.
You can also search this newsgroup and other online
resources for sample code that does what you need
to do, and because it is so basic a task, the odds you
will find plenty of it are fairly good.
If you want first-class service or a drop-in solution,
free free to contact me via email and I'll be more
than happy to give you a quote.
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2008
Supporting AutoCAD 2000 through 2008
http://www.acadxtabs.com