@eyal: It seems you can replace HasLast by TotalPages:
#if($items.HasPreviousPage ) $PaginationHelper.CreatePageLink( 1,
first ) #end
#if(!$items.HasPreviousPage ) first #end
#if($items.HasPreviousPage ) | $PaginationHelper.CreatePageLink
( $items.PreviousPageIndex, prev ) #end
I don't know if anybody else has hit on this but it seems to me like
some documentation somewhere needs to be made better...
I was trying to use this interceptor I wrote [1] in a testing website we
are building. The interceptor is used on a half dozen types and we
needed to know what service
I noticed while build a rather recent trunk revision using the
supplied script, that the AssemblyVersion is fixed at 1.0.3.0. Since I
have a couple of Apps running with the RC3 of Castle (and using the
NHFaclity) and now new Apps using a trunk build they have to life side-
by-side in the GAC.
looks like your nant script can't locate svn.exe
weirdly enough it also happens on my new-ish laptop (a Windows7 thing)
I manually edited my local common.xml to go straight to subversion's folder:
Index: common.xml
===
---
Hi all,
I don't quite understand how does Unity handle different
implementation with different constructors. For example I have an
interface ILog to handle logging functions, there are different
implementations, such as XmlLog, DatabaseLog and so on. In C# code I
may have something like:
You can use fluent interface with Depends on or Parameters stuff.
In xml you can pass them in parameters node IIRC
Tuna Toksöz
http://tunatoksoz.com
http://turkiyealt.net
http://twitter.com/tehlike
Typos included to enhance the readers attention!
On Wed, Mar 4, 2009 at 9:00 PM, Hardy
I am new to Castle, trying to configure the container programmatically
rather than with XML.
I have an interface which has two implementations.
container.AddComponent(importDB, typeof (IPostInboundToDatabase),
typeof (PostAddresses));
container.AddComponent(importFC, typeof
Add the ArrayResolver to the kernel.
container.Kernel.Resolver.AddSubResolver(new ArrayResolver());
On Wed, Mar 4, 2009 at 11:22 AM, Lars Zeb larc...@yahoo.com wrote:
I am new to Castle, trying to configure the container programmatically
rather than with XML.
I have an interface which has
The reason is that if you change the assembly version in every build,
dependant libraries must also be rebuilt or configured with assembly
bindings to use the other version. This is the main reason a lot of
companies won't increment the assembly version for revisions or builds, only
major and
I understand the problem ... but on the other hand is RC3 build not
compatible with a trunk build - at least not if you're using the
NHFacility, because the NHFacility is strictly linked to a specific
version of NH.
So whenever such a strict linking is being changed, the
AssemblyVersion should
Hi,
I have an interesting problem. I have a whole bunch of components,
which are registered in my castle container. I mass-registered them
either based on a certain naming convention or on a common base-
interface they implement. This allows me to register all my components
with just two lines
hmm OK - and how ould I do something like that?
I assume I have to write my own resolver, which can inject this
parameter to my component? If I'm adding such a resolver to my
container, I still will have to tell the resolve the actual value to
inject.
I didn't mention it, because I don't know
Yes, you are right that the assembly version should change as the libraries
move on. The problem is that this is generally something that is done with
an official release, and not changing all the time on the trunk. I'm not
sure how this problem should be fixed while on the trunk without any
13 matches
Mail list logo
