Guidance for building AutofacContrib packages and moving to nuget

[GoogleCodeExporter]

I have a nuspec file for AutofacContrib.Attributed along the lines of the other 
.nuspec files.  That said, I'm not sure if I should be including this into the 
build script.

My questions surround the approach to creating nuspec packages for contrib 
packages - should it be part of the autofac contrib build (I'm not seeing it 
currently) and who is responsible for uploading it to nuget.

I'm happy to work out the details, I just want to make sure I'm pursuing the 
right direction.

Thanks,
-Steve

Original issue reported on code.google.com by steve.he...@gmail.com on 1 Feb 2011 at 2:45

[GoogleCodeExporter]

Hi Steve, sounds good. Under Autofac/src we have a separate Package.build file 
that generates NuGet packages by first running the main Autofac.build script. I 
think something similar for the contrib projects should work. If you plan to 
release the AutofacContrib.Attributed package through NuGet that would be 
great; have a look at David Ebbo's posts on versioning/binding redirects for 
some clues as to how that will work in a model where we don't release 
everything at the same time.

Hope this helps!
Nick

Original comment by nicholas...@gmail.com on 1 Feb 2011 at 10:55

[GoogleCodeExporter]

I'd guess we need one of these for all of the contrib packages. Was just trying 
to get the multitenant and EntLibConfigurator packages and realized we don't 
have them.

I'll probably end up doing this for at least those packages since we've got a 
pressing need for them.

Original comment by travis.illig on 14 Mar 2012 at 4:53

[GoogleCodeExporter]

Issue 354 has been merged into this issue.

Original comment by travis.illig on 21 Mar 2012 at 5:24

[GoogleCodeExporter]

Running into a bit of trouble trying to get things building and running, 
figuring out how to duplicate the process in there. I think there's some 
opportunity to simplify the whole thing, but it would mean looking at issue 252 
- unifying the solution and build structure. More discussion here: 
https://groups.google.com/forum/#!topic/autofac/DH1LsCUE98E

Original comment by travis.illig on 21 Mar 2012 at 7:00

[GoogleCodeExporter]

I'm working on unifying the solution and build so we can have NuGet packages 
for everything. Issue 252. Check the 3.0 branch for the work in progress.

Original comment by travis.illig on 10 May 2012 at 10:08

[GoogleCodeExporter]

I have NuGet up and running for both core Autofac and the Extras in the 3.0 
branch. When 3.0 releases, you should be able to NuGet your way to freedom and 
leisure.

Original comment by travis.illig on 22 May 2012 at 1:03

[GoogleCodeExporter]

The 3.0 branch has been moved to trunk, so development can continue there. We 
have a NuGet package building for every Extras assembly and a very easy way to 
"plug in" new Extras so they can get NuGet packages as well. As soon as we 
release 3.0, it'll all be out there.

I'm going go close this as "fixed" since we've got it nailed, even though it's 
not yet released.

Original comment by travis.illig on 20 Sep 2012 at 3:51

• Changed state: Fixed