I am investigating deriving DataSet for business objects. However, since
datasets may contain several datatables, I need to ensure that the dataset
has a specific table. When casting from a dataset to one of my business
objects, I would like to be able to intercept it and check if this table
exi
I thought about this, but after reading some of the past posting on this
board about this subject, I think it may be more trouble. It sounds like
the code generation is very troublesome. Someone was asking how to insert
logic into the generated code without it being overwritten, and he never
got
This was a feature I really looked forward to using in .Net. However, now
that .Net has finally been released, I haven't found a single book that
talks about it. All the posting about this on this discussion group were
dated before the final release of .Net. MSDN help also states "The
ContextAt
t. I anxiously look forward to fixes
in version 2.0. Or is MS a version 3 company?
-Loc
>>> Jason Kaczor <[EMAIL PROTECTED]> 06/03/02 09:21AM >>>
On Thu, 30 May 2002 12:44:28 -0700, Loc Nguyen <[EMAIL PROTECTED]> wrote:
>board about this subject, I think it may
Has anyone else had a problem with this setting in VS.Net? We are seeing
huge pain in the rear issues with this property setting. We have a multi-
tier application. For development purposes, we have all tiers on each
developer's machine. We have a case where the webservice facade layer
access
Please, anyone? VS.Net assembly is infuriating us, here. The following
is a sample error,
Error: The dependency 'IDBAdapter, Version=1.0.886.27588, Culture=neutral'
in project 'FormTrack' cannot be copied to the run directory because it
would conflict with dependency 'IDBAdapter, Version=1.0.88
Hmm... I remember someone from MS mentioning something about the assembly
version number. I do not remember what it was he said about it. However,
in my second posting to this issue, I mentioned that I did a grep on *.*
at the root of our source tree for the offending version number string and
.Net Assembly Hell is what we've been calling it here. MS will never
learn. Yes, we have gotten it to work by deleting all existing references
in our projects and re-adding them. This is such a nightmare! We have
several dozen projects. The problem would not be so nightmarish if we
could some
Thanks all you who've replied. I faintly remembered an MS guy at one of
their free MSDN presentation specifically discuss not using the wildcard
that the IDE defaults the value to during project generation. I don't
remember the context for this, but I have a feeling assembly hell is the
situatio
