|
RC3: what's in/out
Hey all,
So the 1.0 branch is almost OK, the next step is the Wix setup wizard.
And then it comes down to decide what is going to be on it. We have
the option to include the whole contrib as a separated file (zip) but
that might mislead people to think that we support it. Offering it as
a separated download is another option.
What I like best is to include a few contrib projects that have proven
their value, are documented and supported. I'd like to include,
provided that everyone is OK with that:
- CVSI (need to figure out how)
- ActiveWriter (ditto)
- MR ViewComponents
The other contributions are being left out due to either lack of
documentation of lack of support. I've seen questions popping here in
this list and not being fully appreciated. This can be reviewed for
the 1.0 release, though, so dont need to curse me.
From the main trunk, I'd like to leave some things out. Namely:
- DictionaryAdapter (what is it for anyway?)
- Facilities:
- Cache (stalled)
- Db4o (license issues)
- DynamicLoader (no documentation whatsoever)
- EnterpriseLibrary (stalled)
- iBatisNet (stalled)
- Prevalence (stalled)
- Synchronize (no documentation at all)
- Wcf (no documentation and it's not even a facility)
- ManagementExtensions (stalled)
- Security (stalled)
Obviously, everything is open to discussion.
Thanks
--
Cheers,
hamilton verissimo
hammett@...
http://www.castlestronghold.com/--~--~---------~--~----~------------~-------~--~----~
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-project-devel@...
To unsubscribe from this group, send email to castle-project-devel-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en-~----------~----~----~----~------~----~------~--~---
|
|
Re: RC3: what's in/out
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.
on that notion - +1 for adding CodeGenerator. I'd also like to know what I should do in order to get AspView into the mix. As for value - well we use it at MusicGlue for all our web development, on all our production sites.
I know of at least one solid startup in Israel that had embraced MR only when they were presented with AspView (on my MR/AspView talk). Support - well, I haven't noticed questions about that and I monitor the dev and users list. Nothing in the forum, too (I'm searching for 'AspView' from time to time).
Documentation - well that is probably the problem. I think I could try and duplicate NV and Brail docs and convert the code samples. Is that the missing link? On 9/6/07,
Hamilton Verissimo <hammett@...> wrote:
Hey all,
So the 1.0 branch is almost OK, the next step is the Wix setup wizard.
And then it comes down to decide what is going to be on it. We have
the option to include the whole contrib as a separated file (zip) but
that might mislead people to think that we support it. Offering it as
a separated download is another option.
What I like best is to include a few contrib projects that have proven
their value, are documented and supported. I'd like to include,
provided that everyone is OK with that:
- CVSI (need to figure out how)
- ActiveWriter (ditto)
- MR ViewComponents
The other contributions are being left out due to either lack of
documentation of lack of support. I've seen questions popping here in
this list and not being fully appreciated. This can be reviewed for
the 1.0 release, though, so dont need to curse me.
From the main trunk, I'd like to leave some things out. Namely:
- DictionaryAdapter (what is it for anyway?)
- Facilities:
- Cache (stalled)
- Db4o (license issues)
- DynamicLoader (no documentation whatsoever)
- EnterpriseLibrary (stalled)
- iBatisNet (stalled)
- Prevalence (stalled)
- Synchronize (no documentation at all)
- Wcf (no documentation and it's not even a facility)
- ManagementExtensions (stalled)
- Security (stalled)
Obviously, everything is open to discussion.
Thanks
--
Cheers,
hamilton verissimo
hammett@...
http://www.castlestronghold.com/
--~--~---------~--~----~------------~-------~--~----~
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-project-devel@...
To unsubscribe from this group, send email to castle-project-devel-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---
|
|
Re: RC3: what's in/out
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/--~--~---------~--~----~------------~-------~--~----~
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-project-devel@...
To unsubscribe from this group, send email to castle-project-devel-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en-~----------~----~----~----~------~----~------~--~---
|
|
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/
--~--~---------~--~----~------------~-------~--~----~
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-project-devel@...
To unsubscribe from this group, send email to castle-project-devel-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---
|
|
Re: RC3: what's in/out
Some parts of this message have been removed.
Learn more about Nabble's security policy.
Ok, initial docs on DictionaryAdapter: On 9/6/07, Ken Egozi <egozi13@...> wrote:
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/
--~--~---------~--~----~------------~-------~--~----~
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-project-devel@... To unsubscribe from this group, send email to castle-project-devel-unsubscribe@... For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en -~----------~----~----~----~------~----~------~--~---
|
|
Re: RC3: what's in/out
I'd love to see AW included, but we might have an issue. ActiveWriter source is Apache licensed, but binary release includes DSL Tools redistributable (must), which is under MS' VSIP SDK License. So I licensed the whole setup as "As Is" with the notification below. VSIP SDK allows you to release your code under an OSS license but I'm not sure if we can tag the install binaries as Apache v2. If we can (while stating the exceptional binaries and their license), I can convert it from as is to Apache v2.
VS2008 will have DSL Tools redist (since Linq to SQL also uses it.) and problem will go away, though. ActiveWriter Binaries License:
Except where otherwise noted, all of the documentation and software included
in the ActiveWriter package distributed in binary form is copyrighted by Gokhan Altinoren.
Copyright (C) 2006 Gokhan Altinoren. All rights reserved.
This software is provided "as-is," without any express or implied warranty.
In no event shall the author be held liable for any damages arising from the use of this software.
Permission is granted to anyone to use this software for any purpose and to redistribute source code generated by the tool or binaries compiled from that source code, provided that the following conditions are met:
1. Your usage of the software must not violate Microsoft Visual Studio SDK license.
2. All redistributions in binary form must retain all occurrences of the
above copyright notice and web site addresses that are currently in
place (for example, in the Readme document).
3. The origin of this software must not be misrepresented; you must not claim that you wrote the original software, or rename the binaries. If you use this software to
distribute a product, an acknowledgment in the product documentation
would be appreciated but is not required.
Exceptions: The following files included in ActiveWriter installation distributed in binaries form are subject to the Microsoft Visual Studio SDK License (
http://msdn.microsoft.com/vstudio/extend) (the SDK License):
·
DSLToolsRedist.msi
·
Setup.exe
You are required to agree to terms that protect above items explained in the SDK License mentioned above.
What I like best is to include a few contrib projects that have proven
their value, are documented and supported. I'd like to include,
provided that everyone is OK with that:
- CVSI (need to figure out how)
- ActiveWriter (ditto)
- MR ViewComponents
--~--~---------~--~----~------------~-------~--~----~
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-project-devel@... To unsubscribe from this group, send email to castle-project-devel-unsubscribe@... For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en -~----------~----~----~----~------~----~------~--~---
|
|
Re: RC3: what's in/out
|
|
Re: RC3: what's in/out
I thought about linking from the DA docs to that page, is it ok to do so? (links from docs to 'using', as 'using' is a kinda wiki so the link mught break some day). I would've made a copy of that into the docs, however it might introduce a dependency in a Contrib project.
I think I would anyway add a page about using a baseController<IView, ISession> to achieve TypedSession, TypedF, TypedPB. @hammet: is what I did sufficient to act as docs for that component so it'd make it way into RC3?
On 9/6/07, Lee Henson <lee.m.henson@...> wrote:
FWIW I wrote some docs on the Castle.Tools.CodeGenerator on the using
site a while ago:
http://using.castleproject.org/display/Contrib/Castle.Tools.CodeGenerator
And I've tried to help anyone out who has had difficulties with it,
but I haven't seen many of them.
--~--~---------~--~----~------------~-------~--~----~
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-project-devel@...
To unsubscribe from this group, send email to castle-project-devel-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---
|
|
RE: RC3: what's in/out
I would really like CVSI to be included.
I'm not sure if there is any licensing problems with the
"Microsoft.VisualStudio.*.dll" binaries (in C:\Program Files\Castle Visual
Studio Integration) I have distributed with the setup. We might have to
include a notice similar to what ActiveWriter will have.
CVSI is pretty easy to install, I can send you the *.reg file that needs to
be merged into the registry and then there are a few binaries (2x Castle, 8x
Microsoft) and an icon.
Regards, Jonathon Rossi
> -----Original Message-----
> From: castle-project-devel@... [mailto:castle-project-
> devel@...] On Behalf Of Hamilton Verissimo
> Sent: Thursday, 6 September 2007 1:39 PM
> To: castle-project-devel@...
> Subject: RC3: what's in/out
>
>
> Hey all,
>
> So the 1.0 branch is almost OK, the next step is the Wix setup wizard.
> And then it comes down to decide what is going to be on it. We have
> the option to include the whole contrib as a separated file (zip) but
> that might mislead people to think that we support it. Offering it as
> a separated download is another option.
>
> What I like best is to include a few contrib projects that have proven
> their value, are documented and supported. I'd like to include,
> provided that everyone is OK with that:
>
> - CVSI (need to figure out how)
> - ActiveWriter (ditto)
> - MR ViewComponents
>
> The other contributions are being left out due to either lack of
> documentation of lack of support. I've seen questions popping here in
> this list and not being fully appreciated. This can be reviewed for
> the 1.0 release, though, so dont need to curse me.
>
> From the main trunk, I'd like to leave some things out. Namely:
>
> - DictionaryAdapter (what is it for anyway?)
> - Facilities:
> - Cache (stalled)
> - Db4o (license issues)
> - DynamicLoader (no documentation whatsoever)
> - EnterpriseLibrary (stalled)
> - iBatisNet (stalled)
> - Prevalence (stalled)
> - Synchronize (no documentation at all)
> - Wcf (no documentation and it's not even a facility)
> - ManagementExtensions (stalled)
> - Security (stalled)
>
> Obviously, everything is open to discussion.
>
> Thanks
>
> --
> Cheers,
> hamilton verissimo
> hammett@...
> http://www.castlestronghold.com/>
>
--~--~---------~--~----~------------~-------~--~----~
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-project-devel@...
To unsubscribe from this group, send email to castle-project-devel-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en-~----------~----~----~----~------~----~------~--~---
|
|
Re: RC3: what's in/out
CVSI is a major sell-point for the MR/NV stack. If possible, +2 for including that. On 9/6/07, Jonathon Rossi <jono@...> wrote:
I would really like CVSI to be included.
I'm not sure if there is any licensing problems with the
"Microsoft.VisualStudio.*.dll" binaries (in C:\Program Files\Castle Visual
Studio Integration) I have distributed with the setup. We might have to
include a notice similar to what ActiveWriter will have.
CVSI is pretty easy to install, I can send you the *.reg file that needs to
be merged into the registry and then there are a few binaries (2x Castle, 8x
Microsoft) and an icon.
Regards, Jonathon Rossi
> -----Original Message----- > From: castle-project-devel@... [mailto: ...> devel@...] On Behalf Of Hamilton Verissimo > Sent: Thursday, 6 September 2007 1:39 PM > To: castle-project-devel@...> Subject: RC3: what's in/out > > > Hey all, > > So the 1.0 branch is almost OK, the next step is the Wix setup wizard. > And then it comes down to decide what is going to be on it. We have
> the option to include the whole contrib as a separated file (zip) but > that might mislead people to think that we support it. Offering it as > a separated download is another option. > > What I like best is to include a few contrib projects that have proven
> their value, are documented and supported. I'd like to include, > provided that everyone is OK with that: > > - CVSI (need to figure out how) > - ActiveWriter (ditto) > - MR ViewComponents
> > The other contributions are being left out due to either lack of > documentation of lack of support. I've seen questions popping here in > this list and not being fully appreciated. This can be reviewed for
> the 1.0 release, though, so dont need to curse me. > > From the main trunk, I'd like to leave some things out. Namely: > > - DictionaryAdapter (what is it for anyway?) > - Facilities:
> - Cache (stalled) > - Db4o (license issues) > - DynamicLoader (no documentation whatsoever) > - EnterpriseLibrary (stalled) > - iBatisNet (stalled) > - Prevalence (stalled)
> - Synchronize (no documentation at all) > - Wcf (no documentation and it's not even a facility) > - ManagementExtensions (stalled) > - Security (stalled) > > Obviously, everything is open to discussion.
> > Thanks > > -- > Cheers, > hamilton verissimo > hammett@...>
http://www.castlestronghold.com/> >
--~--~---------~--~----~------------~-------~--~----~
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-project-devel@...
To unsubscribe from this group, send email to castle-project-devel-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---
|
|
RE: RC3: what's in/out
Some parts of this message have been removed.
Learn more about Nabble's security policy.
Thanks,
it’ll get much better in the next month and a bit ;-)
Regards,
Jonathon Rossi
CVSI is a major sell-point for
the MR/NV stack.
If possible, +2 for including that.
On 9/6/07, Jonathon Rossi <jono@...> wrote:
I would really like CVSI to be included.
I'm not sure if there is any licensing problems with the
"Microsoft.VisualStudio.*.dll" binaries (in C:\Program Files\Castle
Visual
Studio Integration) I have distributed with the setup. We might have to
include a notice similar to what ActiveWriter will have.
CVSI is pretty easy to install, I can send you the *.reg file that needs to
be merged into the registry and then there are a few binaries (2x Castle, 8x
Microsoft) and an icon.
Regards, Jonathon Rossi
> -----Original Message-----
> From: castle-project-devel@...
[mailto:...
> devel@...] On
Behalf Of Hamilton Verissimo
> Sent: Thursday, 6 September 2007 1:39 PM
> To: castle-project-devel@...
> Subject: RC3: what's in/out
>
>
> Hey all,
>
> So the 1.0 branch is almost OK, the next step is the Wix setup wizard.
> And then it comes down to decide what is going to be on it. We have
> the option to include the whole contrib as a separated file (zip) but
> that might mislead people to think that we support it. Offering it as
> a separated download is another option.
>
> What I like best is to include a few contrib projects that have proven
> their value, are documented and supported. I'd like to include,
> provided that everyone is OK with that:
>
> - CVSI (need to figure out how)
> - ActiveWriter (ditto)
> - MR ViewComponents
>
> The other contributions are being left out due to either lack of
> documentation of lack of support. I've seen questions popping here in
> this list and not being fully appreciated. This can be reviewed for
> the 1.0 release, though, so dont need to curse me.
>
> From the main trunk, I'd like to leave some things out. Namely:
>
> - DictionaryAdapter (what is it for anyway?)
> - Facilities:
> - Cache (stalled)
> - Db4o (license issues)
> - DynamicLoader (no documentation whatsoever)
> - EnterpriseLibrary (stalled)
> - iBatisNet (stalled)
> - Prevalence (stalled)
> - Synchronize (no documentation at all)
> - Wcf (no documentation and it's not even a facility)
> - ManagementExtensions (stalled)
> - Security (stalled)
>
> Obviously, everything is open to discussion.
>
> Thanks
>
> --
> Cheers,
> hamilton verissimo
> hammett@...
> http://www.castlestronghold.com/
>
>
<br
--~--~---------~--~----~------------~-------~--~----~
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-project-devel@... To unsubscribe from this group, send email to castle-project-devel-unsubscribe@... For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en -~----------~----~----~----~------~----~------~--~---
|
|
Re: RC3: what's in/out
Some parts of this message have been removed.
Learn more about Nabble's security policy.
Yeah - I'd hate to go back to a non-CVSI'ed VS. Both of my thumbs are up too. If only sticking a thumb in the air could make the task easier to do.. Jono - I forgot to mention - I know someone who said he'd buy you a crate of beer when the compiler with intellisense is done. ;-) I'll be reminding him when it is.
Tim. On 06/09/07, Ken Egozi <egozi13@...> wrote:
CVSI is a major sell-point for the MR/NV stack.
If possible, +2 for including that.
On 9/6/07, Jonathon Rossi
<jono@...> wrote:
I would really like CVSI to be included.
I'm not sure if there is any licensing problems with the
"Microsoft.VisualStudio.*.dll" binaries (in C:\Program Files\Castle Visual
Studio Integration) I have distributed with the setup. We might have to
include a notice similar to what ActiveWriter will have.
CVSI is pretty easy to install, I can send you the *.reg file that needs to
be merged into the registry and then there are a few binaries (2x Castle, 8x
Microsoft) and an icon.
Regards, Jonathon Rossi
> -----Original Message----- > From: castle-project-devel@... [mailto: ...> devel@...] On Behalf Of Hamilton Verissimo > Sent: Thursday, 6 September 2007 1:39 PM
> To: castle-project-devel@...> Subject: RC3: what's in/out > > > Hey all, > > So the 1.0 branch is almost OK, the next step is the Wix setup wizard. > And then it comes down to decide what is going to be on it. We have
> the option to include the whole contrib as a separated file (zip) but > that might mislead people to think that we support it. Offering it as > a separated download is another option. > > What I like best is to include a few contrib projects that have proven
> their value, are documented and supported. I'd like to include, > provided that everyone is OK with that: > > - CVSI (need to figure out how) > - ActiveWriter (ditto) > - MR ViewComponents
> > The other contributions are being left out due to either lack of > documentation of lack of support. I've seen questions popping here in > this list and not being fully appreciated. This can be reviewed for
> the 1.0 release, though, so dont need to curse me. > > From the main trunk, I'd like to leave some things out. Namely: > > - DictionaryAdapter (what is it for anyway?) > - Facilities:
> - Cache (stalled) > - Db4o (license issues) > - DynamicLoader (no documentation whatsoever) > - EnterpriseLibrary (stalled) > - iBatisNet (stalled) > - Prevalence (stalled)
> - Synchronize (no documentation at all) > - Wcf (no documentation and it's not even a facility) > - ManagementExtensions (stalled) > - Security (stalled) > > Obviously, everything is open to discussion.
> > Thanks > > -- > Cheers, > hamilton verissimo > hammett@...>
http://www.castlestronghold.com/> >
--~--~---------~--~----~------------~-------~--~----~
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-project-devel@... To unsubscribe from this group, send email to castle-project-devel-unsubscribe@... For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en -~----------~----~----~----~------~----~------~--~---
|
|
RE: RC3: what's in/out
Some parts of this message have been removed.
Learn more about Nabble's security policy.
I
didn’t realise it had such a positive effect. I guess it is probably because I haven’t
done a lot of MR development lately.
A
crate of beer, lol, too bad it would cost more in postage. Maybe I’ll have to
set up a “donate to my open source efforts” like Ayende has ;-)
I
guess intellisense can be shipped with RC4\RTM. However, I’ll be releasing the
binary update releases as I have been lately.
Regards,
Jonathon Rossi
Yeah - I'd hate to go back to a
non-CVSI'ed VS. Both of my thumbs are up too. If only sticking a
thumb in the air could make the task easier to do..
Jono - I forgot to mention - I know someone who said he'd buy you a crate of
beer when the compiler with intellisense is done. ;-) I'll be
reminding him when it is.
Tim.
On 06/09/07, Ken Egozi <egozi13@...> wrote:
CVSI is a major sell-point for the MR/NV stack.
If possible, +2 for including that.
On 9/6/07, Jonathon Rossi <jono@...>
wrote:
I would really like CVSI to be included.
I'm not sure if there is any licensing problems with the
"Microsoft.VisualStudio.*.dll" binaries (in C:\Program Files\Castle
Visual
Studio Integration) I have distributed with the setup. We might have to
include a notice similar to what ActiveWriter will have.
CVSI is pretty easy to install, I can send you the *.reg file that needs to
be merged into the registry and then there are a few binaries (2x Castle, 8x
Microsoft) and an icon.
Regards, Jonathon Rossi
> -----Original Message-----
> From: castle-project-devel@... [mailto:...
> devel@...]
On Behalf Of Hamilton Verissimo
> Sent: Thursday, 6 September 2007 1:39 PM
> To: castle-project-devel@...
> Subject: RC3: what's in/out
>
>
> Hey all,
>
> So the 1.0 branch is almost OK, the next step is the Wix setup wizard.
> And then it comes down to decide what is going to be on it. We have
> the option to include the whole contrib as a separated file (zip) but
> that might mislead people to think that we support it. Offering it as
> a separated download is another option.
>
> What I like best is to include a few contrib projects that have proven
> their value, are documented and supported. I'd like to include,
> provided that everyone is OK with that:
>
> - CVSI (need to figure out how)
> - ActiveWriter (ditto)
> - MR ViewComponents
>
> The other contributions are being left out due to either lack of
> documentation of lack of support. I've seen questions popping here in
> this list and not being fully appreciated. This can be reviewed for
> the 1.0 release, though, so dont need to curse me.
>
> From the main trunk, I'd like to leave some things out. Namely:
>
> - DictionaryAdapter (what is it for anyway?)
> - Facilities:
> - Cache (stalled)
> - Db4o (license issues)
> - DynamicLoader (no documentation whatsoever)
> - EnterpriseLibrary (stalled)
> - iBatisNet (stalled)
> - Prevalence (stalled)
> - Synchronize (n
|
DictionaryAdapter_Initial_Docs.patch (5K)