Announcing Castle.{Transactions, Facilities.AutoTx} v3.1

[Henrik Feldt]

Castle.Transactions v3.1 and Castle.Facilities.AutoTx v3.1 are now ready for downloading from nuget and source from github, like usual!

 

This is the first GA release of version 3.0. It’s compliant with Windsor 3.0.

 

Cheers,

Henrik

 

[Krzysztof Koźmic]

awesome,

well done mate.

@K

--
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 castle-pro...@googlegroups.com.
To unsubscribe from this group, send email to castle-project-d...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.

[hammett]

Cool. What's the nhibernate integration story so far?

--
Cheers,
hammett
http://hammett.castleproject.org/

[jberezanski]

Hi,

 

I'm afraid the published packages are missing several assemblies, Castle.Transactions.nupkg does not even contain any assembly at all.

 

Coincidentally, I noticed this issue yesterday when I tried to build nuget packages for our internal nuget repo from github sources.

 

In rakefile.rb, the nuspec :tx_nuspec task passes wrong pattern to nuspec_copy (the pattern "*Transaction.{dll,xml,pdb}" matched the old Castle.Services.Transaction name, but the assembly is now named Castle.Transactions). Moreover, new assemblies (Castle.IO, Castle.Transactions.IO and their dependency - Mono.Posix) should also be included.

 

As a side note, good job with NLog removal, please continue :)

 

It would also be great if IO and especially Unix/Posix stuff were optional (separate packages) and not required by AutoTx. I understand, however, that it would probably not be trivial.

 

Best regards,

 

Jakub Berezanski

[Henrik]

Hello,

Just wanted to check in pretty late and say that I'm working on this now. There's been a gap in my ability to work on this, as you may have noticed.

Regards,
Henrik

On Saturday, August 11, 2012 4:00:33 PM UTC+2, Stu wrote:

I posted about this on Stack Overflow (see here:  http://stackoverflow.com/questions/11913331/installing-castle-transactions-from-nuget-doesnt-produce-a-dll ) as this is still a problem.  Unfortunately I haven't been able to resolve the problem and I think the main reason for that is that Castle has also had an update in the past few days.  Trying to manually resolve this by installing older versions of various packages is a dependency nightmare that I haven't beaten.

Does anyone have any idea how to fix this?  Is it only Henrik that can accept the pull request and deploy to NuGet?  I dropped him an email the other day to tell him that this was an issue but I haven't had a response yet.

Thanks

Stu

[Henrik]

v3.2 targeting the new Windsor released. They should indeed contain dlls this time. ^^