July 2003 - Posts
They are calling
this Social Software
I have seen a few
questions popping up on LISTSERVs about ADO.NET. Mainly concluding that
ADO.NET is more difficult when compared to ADO 2.6 and
RecordSets.
All I can say is deal
with the extra work and the learning curve as it is well worth the time and
effort. Spend some time in the SDK and pick up Essential ADO.NET and
read it from cover to cover. I have struggled with losing cursors, but
overall a disconnected ResultSet is MONEY.
[Now Playing: Duran Duran - Save a Prayer [US Single Version] (03:47)]
It is nice to see I am
now part of the 'Wrox Author Team' vs. being an individual....
http://www.amazon.com/exec/obidos/tg/detail/-/1861008465/qid=1058287182/sr=1-1/ref=sr_1_1/002-0462371-3880820?v=glance&s=bookshtm
Anyone out there
getting paid for their .NET book contributions by the way? Good thing I
kept my daytime job ;-)
If you are building a
Windows Forms App that needs to use grids, run, do not walk to Janus Systems and
purchase the GridEX NOW! I do not work for them. I do not even know
them. This Grid is MONEY and worth every dollar you spend one
it. The support is incredible and the functionality built into this Grid
blows me away every day.
[Now Playing: R.E.M. - Texarkana (03:40)]
We have seen cases
where the IDE, on a Build, will somehow change the version of a reference
dll. An example is this:
c:\myapp\bin\my.dll (v
1.00)
c:\myapp\bin\my.dll (v
2.00)
We reference (File) v
1.00 in the IDE. Another file in the same project needs v 2.00. On a
build, the ide will change the reference from v 1.0 to v 2.0. Now, the
file that needs v 1.00 generate build errors as it is no longer
referenced. How, in this case where I need to reference both versions, do
I do this from with the IDE?
More Posts