Why not? On Wed, Oct 6, 2010 at 11:33 PM, Fabio Maulo <fabioma...@gmail.com> wrote:
> Can we give support even for System.Uri ? > > > On Wed, Oct 6, 2010 at 6:30 PM, Fabio Maulo <fabioma...@gmail.com> wrote: > >> Or you may think that .Net3.5 mean .Net3.5 and then discover that there is >> a .Net3.5 but... "Client Profile"where something was removed. >> In general each dependency is a PITA internal to .NET framework or >> external it is a PITA... the internals to the .NET framework are a PITA a >> little bit small but a PITA. >> >> >> On Wed, Oct 6, 2010 at 6:25 PM, Fabio Maulo <fabioma...@gmail.com> wrote: >> >>> Well... you may have a dependency to mscorelib and then discover that >>> there is another mscorelib where something is missed. >>> O no? >>> >>> >>> On Wed, Oct 6, 2010 at 6: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 >>>>>> >>>>>> >>>>> >>>> >>> >>> >>> -- >>> Fabio Maulo >>> >>> >> >> >> -- >> Fabio Maulo >> >> > > > -- > Fabio Maulo > >
