Hello,
I have revisited Astoria lately, and found that Astoria *does*
depend on Linq to Entities. The statement that Astoria works over
_any_ linq binding is wrong. It rejects such IQueryable that
does not conform to Linq to Entities manner. For example, change
ID column name as ID_. It rejects
Oops, I've sent my draft instead of the finished one. I'm resending it -
Hello,
I'm replying to an old post.
I have revisited Astoria lately, and found that Astoria *does*
depend on Linq to Entities. (i.e. unlike the previous discussion,
The statement that Astoria works over _any_ linq binding
On Mon, Jul 27, 2009 at 9:48 PM, Gladish, Jacobjacob.glad...@sig.com wrote:
I decided to give xbuild a try today and was pretty impressed on how well it
was working.
Glad to hear that :)
I have a project with a few .config files checked into revision control that
wind up being read-only.
Hello
Mono SVN trunk build failed.
$ gmake
(snip)
gmake[6]: Entering directory `/export/home/ksmakoto/Mono/mcs/class'
gmake[7]: Entering directory `/export/home/ksmakoto/Mono/mcs/class/corlib'
gmake all-local
gmake[8]: Entering directory `/export/home/ksmakoto/Mono/mcs/class/corlib'
MCS
Hi,
On 7/28/09, KISHIMOTO, Makoto ksmak...@dd.iij4u.or.jp wrote:
Mono SVN trunk build failed.
This is fixed already,
Thanks!
--
Jb Evain j...@nurv.fr
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
But it's a pretty straight forward use case. I sync my code from revision
control. In this particular case, I'm using perforce. Perforce brings files
down from the depot read-only. To edit, you must check out files. My log
configuration is sync'd up read only. I build and the file gets moved
Hello,
So, just to make everything clear beforehand, the whole ParallelFx patch
only add new classes and so, apart from the build system, no legacy files is
touched.
At first, the process I was thinking of about the whole patch is that people
interested to review would apply it directly to a
Hello Jérémie,
Why are the files in System.Core, could we not put the files in
their final location (which seems to be mscorlib) from the start?
Miguel seems to have the same idea as me apart that I commit the new
types directly instead of providing a patch.
The new types can be added
Hey,
On 28 Jul 2009, at 18:36, Miguel de Icaza mig...@novell.com wrote:
Hello Jérémie,
Why are the files in System.Core, could we not put the files in
their final location (which seems to be mscorlib) from the start?
Fromyalkibg to jeremie earlier, i think it's partially because of
Hello,
Why are the files in System.Core, could we not put the files in
their final location (which seems to be mscorlib) from the start?
Fromyalkibg to jeremie earlier, i think it's partially because of
legacy reasons. Some of the parallel fx files already exist in that
location
Hi,
Hello Jérémie,
Why are the files in System.Core, could we not put the files in
their final location (which seems to be mscorlib) from the start?
Fromyalkibg to jeremie earlier, i think it's partially because of
legacy reasons. Some of the parallel fx files already exist in
Hey,
On 28 Jul 2009, at 22:07, Miguel de Icaza mig...@novell.com wrote:
Hello,
Why are the files in System.Core, could we not put the files in
their final location (which seems to be mscorlib) from the start?
Fromyalkibg to jeremie earlier, i think it's partially because of
legacy
12 matches
Mail list logo
