I downloaded the sources and all files are there. As I said -
Silverlight projects weren't kept up to date so some files may have
changed location, but they are all there.
That's the kind of problems we want to address with SolutionTransform.
Currently you have to do it manually :/
Krzysztof
On 2010-04-11 11:15, Michael Sync wrote:
And also Castle.Core.Internal.Lock is not in Silverlight version Core
1.2.0.
Thanks and Best Regards,
Michael Sync
Don't go the way life takes you.
Take life the way you go
http://michaelsync.net
2010/4/11 Michael Sync <[email protected] <mailto:[email protected]>>
DP 2.2 is using IAttributeDisassembler and Core 1.2.0 doesn't have
that interface. Is there any stable version of Core that works
well with DP 2.2?
Thanks and Best Regards,
Michael Sync
Don't go the way life takes you.
Take life the way you go
http://michaelsync.net
2010/4/11 Michael Sync <[email protected]
<mailto:[email protected]>>
>>only exposed to external consumption
yes. but you have the unit tests to ensure those classes are
correct right? :) Your CI should run the unit tests as well..
Thanks and Best Regards,
Michael Sync
Don't go the way life takes you.
Take life the way you go
http://michaelsync.net
2010/4/11 Krzysztof Koźmic <[email protected]
<mailto:[email protected]>>
That's easier for an application than for a framework.
In framework it is OK to have classes that are not used
internally, only exposed to external consumption
(especially in low level project like Core).
Thanks for the link to Project Linker, I'll have a look.
Krzysztof
On 2010-04-11 10:50, Michael Sync wrote:
Let's say you have a class "A" in both .NET and SL.
Our continuous integration ensure that both solution are
able to compile.
And developer added new class called B in .NET but he
forget to add it in SL.. But you are not using that class
"B" anyway. So, it's okay for both version. and our CI is
happy too.
But you start using class "B" in class "A" then the CI
will not be able to compile SL version because the
dependency class B is missing in SL. and CI will send the
notification to developers so we knows and we will add
class "B" as a link in Silverlight. Then, the CI will be
able to compile both projects.
You can also take a look at Composite Application Library
(Prism)
http://www.microsoft.com/downloads/details.aspx?FamilyID=387c7a59-b217-4318-ad1b-cbc2ea453f40&displaylang=en
<http://www.microsoft.com/downloads/details.aspx?FamilyID=387c7a59-b217-4318-ad1b-cbc2ea453f40&displaylang=en>
that
supports both .NET and SL. They also have something
called Project Linker.
Thanks and Best Regards,
Michael Sync
Don't go the way life takes you.
Take life the way you go
http://michaelsync.net
2010/4/11 Krzysztof Koźmic <[email protected]
<mailto:[email protected]>>
How do you ensure that your solution files for .NET
and SL are in sync, i.e. if someone adds a new class
to .NET solution he/she didn't forget to add the same
class to SL solution?
Krzysztof
On 2010-04-11 10:35, Michael Sync wrote:
I'm not a developer of Moq but I've done a few
Business projects that we support both .NET (WPF)
and Silverlight. We used to have one solution file
for each version. And we are using Hudson CI to
auto-build both .NET version and SL version based on
Solution file. So, we can ensure that if it's
working fine in CI (Continuous Integration) then it
will be working file in Visual Studio as well.
(Developers uses sln file in VS so it's very
important for us to ensure that our sln files are
working files and no missing file. )
Thanks and Best Regards,
Michael Sync
Don't go the way life takes you.
Take life the way you go
http://michaelsync.net
2010/4/11 Krzysztof Koźmic
<[email protected]
<mailto:[email protected]>>
Yeah,
we used to build our Silverlight version without
solution using NAnt.
Now we use MsBuild and experiment with a tool
written by Julian
(http://github.com/JulianBirch/Solution-Transform)
to generate Silverlight solutions off of .NET
solutions. This is still very much a prototype
and we don't have it integrated yet.
You may try to get it working (see this docs:
http://using.castleproject.org/display/Contrib/Solution+Transform
) or ping Julian
but you may end up having to redo it manually.
BTW, while we're on it - how do you plan to keep
.NET Moq and SL Moq in sync?
Krzysztof
On 2010-04-11 10:21, Michael Sync wrote:
It's very easy to port Castle.Core 1.2 but the
problem started with Dynamic
2.2.0. DynamicProxy2-Silverlight.sln doesn't
work. A lot of files are missing.
Thanks and Best Regards,
Michael Sync
Don't go the way life takes you.
Take life the way you go
http://michaelsync.net
2010/4/11 Krzysztof Koźmic
<[email protected]
<mailto:[email protected]>>
Why do you need the source?
Anyway,
here's 2.2 tag for DP:
http://github.com/castleproject/Castle.DynamicProxy/tree/2.2.0
here's 1.2 tag for Core:
http://github.com/castleproject/Castle.core/tree/1.2.0
Krzysztof
On 2010-04-11 10:12, Michael Sync wrote:
Hello Krzysztof,
Thanks.
I would like to get the *source code* of
Castle.Core and DynamicProxy Silverlight
version. Could you please give me the
download links? Thanks.
Thanks and Best Regards,
Michael Sync
Don't go the way life takes you.
Take life the way you go
http://michaelsync.net
On Sun, Apr 11, 2010 at 4:06 PM, Michael
Sync <[email protected]
<mailto:[email protected]>> wrote:
Hi,
I downloaded Release-Jan-06
<http://github.com/castleproject/Castle.Core/archives/Release-Jan-06> now.
There are a lot of things inside but I
can't find Silverlight solution for
Core and DynamicProxy. Is there any
solution file for Core and
DynamicProxy in that release?
Thanks and Best Regards,
Michael Sync
Don't go the way life takes you.
Take life the way you go
http://michaelsync.net
2010/4/11 Krzysztof Koźmic
<[email protected]
<mailto:[email protected]>>
Use released version,
trunk is undergoing major
restructuring at the moment and it
may not function properly.
Krzysztof
On 2010-04-11 09:23, Michael Sync
wrote:
Hello,
I think it's good that you
guys are supporting
Silverlight version.
Sharing the build that can't
even compile is not a bit weird. I
downloaded
"castleproject-Castle.Core-f645bab.zip"
and open
DynamicProxy2-Silverlight.sln
and there are a lot of missing
files and
even csproj.
--
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]
<mailto:[email protected]>.
To unsubscribe from this group,
send email to
[email protected]
<mailto:castle-project-devel%[email protected]>.
For more options, visit this group
at
http://groups.google.com/group/castle-project-devel?hl=en.
--
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]
<mailto:[email protected]>.
To unsubscribe from this group, send email
to
[email protected]
<mailto:[email protected]>.
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en.
--
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]
<mailto:[email protected]>.
To unsubscribe from this group, send email
to
[email protected]
<mailto:castle-project-devel%[email protected]>.
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en.
--
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]
<mailto:[email protected]>.
To unsubscribe from this group, send email to
[email protected]
<mailto:[email protected]>.
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en.
--
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]
<mailto:[email protected]>.
To unsubscribe from this group, send email to
[email protected]
<mailto:castle-project-devel%[email protected]>.
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en.
--
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]
<mailto:[email protected]>.
To unsubscribe from this group, send email to
[email protected]
<mailto:[email protected]>.
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en.
--
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]
<mailto:[email protected]>.
To unsubscribe from this group, send email to
[email protected]
<mailto:castle-project-devel%[email protected]>.
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en.
--
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]
<mailto:[email protected]>.
To unsubscribe from this group, send email to
[email protected]
<mailto:[email protected]>.
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en.
--
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]
<mailto:[email protected]>.
To unsubscribe from this group, send email to
[email protected]
<mailto:castle-project-devel%[email protected]>.
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en.
--
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.
--
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.
