+1 On Wed, Oct 6, 2010 at 11:16 PM, Rory Plaire <codekai...@gmail.com> wrote:
> System.Xml.Linq is in .Net v3.5 and .Net v4.0 Client and above. Taking a > dependency should pose no problem if .Net 3.5 is required. > > The difference between a dependency on a subpart of the framework and the > framework as a whole seems to me to be nothing. > > -r > > On Wed, Oct 6, 2010 at 2:08 PM, Pablo Ruiz <pablo.r...@gmail.com> wrote: > >> If the fix is trivial.. I would avoid referencing Sys.Xml.Linq.. Maybe as >> an external IUserType or as part of NhuAddIns? >> >> >> On Wed, Oct 6, 2010 at 11:03 PM, Fabio Maulo <fabioma...@gmail.com>wrote: >> >>> http://216.121.112.228/browse/NH-2342 >>> >>> <http://216.121.112.228/browse/NH-2342>Opinions about the introduction >>> of a dependency to System.Xml.Linq ? >>> The fix is trivial but I would avoid another dependency even if it is >>> part of ".Net" framework (which one of the .Net frameworks only God and >>> Microsoft know) >>> >>> -- >>> Fabio Maulo >>> >>> >> >