OK, I'll investigate the possibility and switch Core and Windsor to CP
On 2010-04-13 05:39, Simon wrote:
RE client profile
First some background http://msdn.microsoft.com/en-us/library/cc656912.aspx
OK this is my understanding of the "client profile" versions is that
if you can build against the "client profile" you should.
The reason being is that is it works against the "client profile" it
will work against the full version
This is echoed by the accepted answer here
http://stackoverflow.com/questions/15694/is-the-net-client-profile-worth-targetting
One point to note is that Rhino mocks seems to use things not included
in the client profile so your unit test projects will need to target
the full version. Not a big issue since you dont deploy these.
On Apr 12, 5:46 pm, Krzysztof Koźmic (2)<[email protected]> wrote:
Just to make a (more or less) comprehensive list of runtimes we
*could* support:
.NET 3.5 sp1 (full)
.NET 3.5 sp1 (client profile)
.NET 4 (full)
.NET 4 (client profile)
.NET 4 (web profile) //IIRC I saw this option in VS10beta2
SL 3.0
SL 4.0
Mono 2.6 +
CF and SL-Wp7 are out due to lack of lots of crucial API. We could
produce a crippled version (no dynamic proxy) but that's massive
effort.
On 12 Kwi, 02:25, James Curran<[email protected]> wrote:
Um... There are different CPUs involved. No Desktop Windows
executable works on Mobile Windows.
Truth,
James
2010/4/11 John Simons<[email protected]>:
You have to be fu?$ing joking!
Another version of Silverlight, that is all we need! Can I get my own
version too!
Bad MS bad.....
--
You received this message because you are subscribed to the Google Groups "Castle
Project Development List" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en.
