But the issue you seem to be side-stepping with this .NET raving you're so
keen on, is that the runtime environment is too demanding for all but the most
powerful PCs at the moment. The runtime needs about 128MB RAM for starters,
and at least a P3-800 to run reasonable well. It won't go on Win9x, and now
there are 2 very different versions out 1.1 and 2.0 which even have different
language constructs, so compatibility between these 2 versions is already an
issue. Microsoft have done this in true "SP2" style - an absolutely shoddy
show, with lots of user fallout. I'm sorry, but the best advice anyone can
give about .NET (especially if you are *NOT* doing anything ASP) is to wait
"Alisdair Meredith [TeamB]"
| > So might it not be fortuitous to perchance, wait until the .NET
| > toolsets are more evolved and easy to port BCB projects over to? Say,
| > 5 years hence? --
| Yes and no. Imagine how much more functional your software will become
| in 5 years? What you gain while waiting for the better development
| environment to appear is offset by the extra work you are adding all
| the time!
| That is where attention to classic design details, such as separation
| of UI / app logic / database access pays off. If the core of your
| system is portable C++, you only have to port the environment specific
| parts (GUI and Database-layer) If you can find a portable solution for
| these parts, even better!
| This is also where something like VCL.NET is extremely useful. It
| might not be the identical library to Win32, it may not show off all
| the whizzy new .NET GoodnessTM, but it is the 90% solution that gets
| you up and running on the platform in next to no time. Then it is your
| choice whether you need to investigate a different long-term solution,
| but at least you have arrived.