These are chat archives for damianh/Cedar

4th
May 2015
João Bragança
@thefringeninja
May 04 2015 08:58
https://www.myget.org/F/dh/ <- is this where i can find everything
Set this up on Friday
João Bragança
@thefringeninja
May 04 2015 08:59
ty
Damian Hickey
@damianh
May 04 2015 09:00
blob
Doing Domain.Projections package CI & package atm; then Cedar.EventStore.
João Bragança
@thefringeninja
May 04 2015 09:05
install-package -pre Cedar.CommandHandling.Http.Client eVision.ShiftVision
install-package : Unable to find package 'Cedar.CommandHandling.Http.Client'.
nuspecs in source control seem fine tho
Damian Hickey
@damianh
May 04 2015 09:06
Hmm Trying it out now
João Bragança
@thefringeninja
May 04 2015 09:06
nuget package explorer says they are up there
but it also says that the version number is 1.0.0-build00020 yet when i installed Cedar.CommandHandling i get 1.0.0-build00080
i will try and specify the version number
Damian Hickey
@damianh
May 04 2015 09:07

PM> install-package -s https://www.myget.org/F/cedar/api/v2 -Prerelease Cedar.CommandHandling.Http.Client
Installing 'Cedar.CommandHandling.Http.Client 1.0.0-build00020'.
Successfully installed 'Cedar.CommandHandling.Http.Client 1.0.0-build00020'.
Adding 'Cedar.CommandHandling.Http.Client 1.0.0-build00020' to ClassLibrary2.
Successfully added 'Cedar.CommandHandling.Http.Client 1.0.0-build00020' to ClassLibrary2.

PM>

package sources messed up
I'll delete all Cedar packages from dh feed.
João Bragança
@thefringeninja
May 04 2015 09:08
wat
specifying the feed manually works
Damian Hickey
@damianh
May 04 2015 09:09
yep
cleaning that up now.
Next build will be 81
For Cedar.CommandHandling.*
This will fix any cached package problems.
Damian Hickey
@damianh
May 04 2015 09:15
I want to ship Cedar.CommandHandling alpha by end of week.
@thefringeninja did we agree to kill Cedar.Projections.Testing (for now)?
João Bragança
@thefringeninja
May 04 2015 09:22
Cedar.CommandHandling does not appear to have that new version number
should I worry about it
yes
Damian Hickey
@damianh
May 04 2015 09:24
On the package or assembly version or where?
blob
did we agree to kill Cedar.Projections.Testing (for now)?
João Bragança
@thefringeninja
May 04 2015 09:25
yes
Damian Hickey
@damianh
May 04 2015 10:57
Cedar.Projections on the CI feed now.
Cedar.EventStore next (but will be unusable for a while)
Damian Hickey
@damianh
May 04 2015 11:12
@yreynhout Added you here, hope you don't mind.
Damian Hickey
@damianh
May 04 2015 13:13
I've pulled the IAggregateFactory and repository related stuff from Cedar.Domain. For now at least, there won't be any repository related items in any of the Cedar.*. There has been some debate on how AR should be activated (ctor vs factorymethods) as well as generic repository vs repository per Ag.
Since no clarity at this point, not going to prescribe any particular way.
Damian Hickey
@damianh
May 04 2015 13:19
@thefringeninja going to release the current Cedar.Domain build as 0.3, so there is a "stable" build to work off.
João Bragança
@thefringeninja
May 04 2015 13:32
k
Damian Hickey
@damianh
May 04 2015 13:58
blob
@thefringeninja Bit of a rename in the projections stuff inbound.
João Bragança
@thefringeninja
May 04 2015 18:27
lol. it works but i found a bug in my code
actually it's a pretty serious one. the root of the problem is that the eventstore client api doesn't do async
so we had to hack a work around. iirc their client api does back pressure for you on subscriptions. but because we're shovelling these into our own 'async queue' thingy
it'll just fill it up without bounds. hrm