Re: RC3: what's in/out

1. I'll try to start doc-ing the DictionaryAdapter. Never xdoc-ed so I hope it's go smooth.
2. I agree that it adds a bit of complexity, as you need to setup the msbuild target, and to setup the msbuild task to your web's csproj. But it's a one time setup fee, that turns monorail development into much more fun. I'd try and write at least a blog post about it.
3. AspView's trunk is matching Castle's trunk.

There is a branch of AspView that relies on MR-302, as it adds support for using multiple CompiledViews assemblies, and it needs 302 that is needed so the view sources won't need to reside on the website's filesystem.

On 9/6/07, Hamilton Verissimo <hammett@...> wrote:

On 9/6/07, Ken Egozi <egozi13@...> wrote:
> DictionaryAdapter is a very useful utility that generates a typed wrapper
> (based on an Interface Hierarchy) around dictionaries.
>
> I'd vote -1 for leaving that out. Besides, anyone who uses the CodeGenerator
> is using that one too.

Fair enough. But I'd need that it be documented. The stub is right
here https://svn.castleproject.org/svn/castle/site/xdocs/components/dictionaryadapter/index.xml

> on that notion - +1 for adding CodeGenerator.

More than often I see people bringing complains and problems about it,
and I dont see most of them being replied. It also adds a layer of
complexity that I'd rather leave for people that stand in a different
level, enough to grab it and make it work themselves with the aid of
some documentation or blog post.

> I'd also like to know what I should do in order to get AspView into the mix.

Does it work with the trunk code? I remember that you said you have a
different version of the trunk with some changes applied.

--
Cheers,
hamilton verissimo
hammett@...
http://www.castlestronghold.com/