ch may
clarify some ideas mentioned here.
Thanks,
Avantika
-Original Message-
From: Ben Dewey [mailto:ben.de...@26ny.com]
Sent: Friday, June 12, 2009 2:20 PM
To: 'stonehenge-dev@incubator.apache.org'
Subject: RE: [jira] Updated: (STONEHENGE-66) Create a .NET Config Servic
009 5:52 PM
To: Stonehenge Development
Subject: RE: [jira] Updated: (STONEHENGE-66) Create a .NET Config Service
There is probably an already established precedence but my vote would be to
only commit completed code. If I want to test the current code I can do so from
the patch.
Just my 2
...@hotmail.com]
Sent: Friday, June 12, 2009 2:52 PM
To: Stonehenge Development
Subject: RE: [jira] Updated: (STONEHENGE-66) Create a .NET Config Service
There is probably an already established precedence but my vote would be to
only commit completed code. If I want to test the current code I can do so from
: Fri, 12 Jun 2009 17:30:53 -0400
> Subject: RE: [jira] Updated: (STONEHENGE-66) Create a .NET Config Service
>
> In regards to the items needed in the future (ie set/get DbConfig):
>
> What's the procedure for commiting code that has two parts or planned
> upgrades?
>
In regards to the items needed in the future (ie set/get DbConfig):
What's the procedure for commiting code that has two parts or planned upgrades?
Should we avoid committing a bunch of commented-out code?
Should we just commit code that’s directly applicable?
-Ben
-Original Message-
Avantika,
Great start, Here is a list of some comments.
- The Config Configuration Settings should really only include DB
connString/user/password
- Same for the ConfigConsole App.config
- don't include your .sou files in the patches (they fail anyways)
- The IDAL, DALFac, DALSql Config.cs and
