David,
Firstly I'll tell you that in vs.net 2005 things are going to be a lot
better. Currently vs.net 2003 has many odd behaviours. BUT.... regardless
of some very annoying features, it's still a very nice program to use.
Let me tackle some of your requirements here:
-Business rules library: up to your coding, although vs.net is very
intuitive at a 2-tier solution, it can easily be used to make n-tier
solutions.
-Resizeable forms: yes
-Multi-lingual: from what perspective?? You can code in any .net language
and a few non .net languages.
-Easily transported to PDA / web application: Easier than it would be in
some environments. The framework allows for good platform independant
coding.
-Database independant: yes
-User enabled Form designer: possibly, at least it would be possible to do
this with a grid layout and some customisable options. .Net V2 may make
this even easier, it certainly will from a web perspective.
-Modularised deployment with easy deployment of small patches: I believe
its possible to do incremental patching, but I'm not sure if this is a
standard feature.
-Real time web lookup: yes
-Source code security: It has options for integrated source control
software. This is an add-on from MS
-Able to be developed in no time flat: I guess you could call it a RDE,
nothings ever fast enough for the boss though is it? :D
-Self error checking or at least, easy to error check / test for new
releases: The environment will give you some indication of errors, but you
are far better off going the route of a dedicated testing platform.
-Fast performance with large data sets: more to do with your DB engine here.
As a note, SQL2003 is reporting very significant gains over 2000, and it'll
be a .net product allowing a lot closer integration significantly easier
than currently.
It really IS a good choice of development platform. And if you don't know
exactly what it is you want to do, intellisence is a godsend and a good 70%
of the time you find the object/method you needed.
However, no-one has managed to improve upon the sheer power of Notepad.
--
Adam Smith
> I am a veteran FoxPro developer who loved BFP but has decided that our large
> commercial project that is extremely rich and complex in many ways and is
[quoted text clipped - 53 lines]
> David Younger
> The Service Manager
Thomas H - 26 Jul 2004 16:38 GMT
Adam,
Actually, I find Textpad to be my runner-up; it came with a book I bought 3
years ago, and I've been using it ever since!
David, you can use, and program in, the .NET framework without buying
VS.NET- like Adam said, all you need is a text editor. You could evaluate
the .NET framework first, then buy VS.NET later. Look for the .NET SDK from
Microsoft's downloads.
-Thomas
> However, no-one has managed to improve upon the sheer power of Notepad.
>
[quoted text clipped - 67 lines]
> > David Younger
> > The Service Manager
Adam Smith - 27 Jul 2004 11:02 GMT
Personally I use a mix of VS.net, Ultraedit and the .NET Webmatrix.
If you want to have a fiddle with .net before you consider buying into it,
try out the .net webmatrix from www.asp.net (also a couple of nice funky
examples). While webmatrix is no where near as complicated as vs.net, it
contains a surprising amount of functionality considering its freeware.
Why do I use both VS.NET and Webmatrix? Well this is because of one of
vs.net's annoying features. You can't compile individual classes into their
own assemblies. VS.NET forces the entire project into one assembly. So....
I use vs.net for the rapid development and then webmatrix for the subtle
changes needed for individual assemblies.
--
Adam Smith
> Adam,
>
[quoted text clipped - 84 lines]
> > > David Younger
> > > The Service Manager