Cool, I'll take a look when I can - probably next week. I've skimmed the
thread you sent and it looks very relevant will look again when I'm not so
tired.

 

Thanks

 

Mark 

 

From: [email protected]
[mailto:[email protected]] On Behalf Of Roelof Blom
Sent: Friday, 19 June 2009 9:22 p.m.
To: [email protected]
Subject: Re: Dynamic Proxy - Silverlight Build

 

Thanks for the patch.

In r5782 the DP/SL unit test has been commited, it seems that this project
has never been added to SVN, see r5493.

See also this mailing list thread:
http://groups.google.com/group/castle-project-devel/browse_thread/thread/54f
25b1c49f2f110/ba01b243533f263e

-- Roelof.

On Fri, Jun 19, 2009 at 4:48 AM, Mark <[email protected]> wrote:

So to get \Tools\Castle.DynamicProxy2\DynamicProxy2-Silverlight.sln to
compile I only have to add in the missing 'UpgradableLock.cs' class (as per
attached patch).

 

However, the tests folder is missing so I get an error when opening the
solution because this project is missing:

 

\Tools\Castle.DynamicProxy2\Castle.DynamicProxy.Silverlight.Tests\Castle.Dyn
amicProxy2.Silverlight.Tests.csproj

 

 

Can someone add that folder to SVN? 

 

Otherwise it's going to be difficult to get the tests passing ;-).

Thanks

 

Mark

 

 

From: Mark [mailto:[email protected]] 
Sent: Thursday, 18 June 2009 8:18 a.m.


To: '[email protected]'

Subject: RE: Dynamic Proxy - Silverlight Build

 

I just updated to latest version (r5779). When I open
\Tools\Castle.DynamicProxy2\DynamicProxy2-Silverlight.sln I get a message
saying a project
(\Tools\Castle.DynamicProxy2\Castle.DynamicProxy.Silverlight.Tests\Castle.Dy
namicProxy2.Silverlight.Tests.csproj) can't be found (and I can't find that
project ion source anywhere).

 

Also when I try to compile I get 6 errors all relating to 'UpgradableLock'
being missing e.g.

 

Error   11      The type or namespace name 'UpgradableLock' could not be
found (are you missing a using directive or an assembly reference?)
E:\DevPlay\Castle\Tools\Castle.DynamicProxy2\Castle.DynamicProxy\InternalsHe
lper.cs        33      11          DynamicProxy2-Silverlight

 

 

 

Am I doing something wrong?

 

Thanks

 

Mark

 

 

From: [email protected]
[mailto:[email protected]] On Behalf Of Roelof Blom


Sent: Thursday, 18 June 2009 3:10 a.m.

To: [email protected]
Subject: Re: Dynamic Proxy - Silverlight Build

 

The patch has been applied in r5776, thanks.

Also, DP for SL compiles again from r5778 onwards.

-- Roelof.

On Wed, Jun 17, 2009 at 2:13 AM, DAVIS, Peter <[email protected]>
wrote:

Once the patches attached in this issue are resolved, then core will compile
straight from svn. 

 

http://support.castleproject.org/projects/CORE/issues/view/CORE-ISSUE-23

 

I have not looked at DP yet, but at least that project is correctly linked
to silverlight assemblies, unlike micro kernel and Windsor.

 

Pete

 

  _____  

From: [email protected]
[mailto:[email protected]] On Behalf Of Jonathon Rossi
Sent: Monday, 15 June 2009 6:36 PM


To: [email protected]
Subject: Re: Dynamic Proxy - Silverlight Build

 

Sure, no problem.

On Mon, Jun 15, 2009 at 6:11 PM, Mark <[email protected]> wrote:


This may be a bit chicken-and-egg but I'd rather not go fixing unit
tests until I was sure the code was in the correct state (which I'm
not sure mine is).
Can you let me know when the code compiles straight from SVN? I'll
take a look at the tests then.

Cheers

Mark


On Jun 15, 12:24 pm, Jonathon Rossi <[email protected]> wrote:
> There are many unit tests that aren't successful on silverlight. It would
be
> really helpful if we can get these fixed in both Castle Core and DP2.

 

 





--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to