Add an option to use unstable package feed #183

Closed
DamianEdwards opened this Issue Jun 18, 2015 · 2 comments

Projects

None yet

3 participants

@DamianEdwards

It would be great if the project generators had an option to use the unstable package feed (aspnetvnext). This would drop a nuget.config file in the project folder configured to use the feed (e.g. like this) as well as setting the package dependencies versions in project.json to * instead of locked to a specific version, e.g. 1.0.0-* instead of 1.0.0-beta4.

@sayedihashimi
Member

How about adding a sub-generator (i.e. item template)? I think adding the sub-gen would be simpler, we can add the option as well to the generator but that may take more time.

Can you paste the content of the nuget.config file that you are looking for?

@peterblazejewicz
Contributor

Something like would be OK, it's commonly used solution I believe:

yo aspnet [...] --unstable

The subgenerator option can also work, it could:

  • read project.json (if exists), make change and write back
  • copy config file
@peterblazejewicz peterblazejewicz added a commit to peterblazejewicz/generator-aspnet that referenced this issue Nov 23, 2015
@peterblazejewicz peterblazejewicz 🎨 Add unstable NuGet config option. Closes #183
- add conditional option to NuGet subgenerator
- update tests to cover unstable feed generation
- update tests helper to support no-content assertion
- update documention and usage files

With this commit the users will be able to generate NuGet config file
with unstable feed to support pre-release development - e.g. when updating
this generator :)
72ecad5
@peterblazejewicz peterblazejewicz added a commit to peterblazejewicz/generator-aspnet that referenced this issue Nov 23, 2015
@peterblazejewicz peterblazejewicz 🎨 Add unstable NuGet config option. Closes #183
- add conditional option to NuGet subgenerator
- update tests to cover unstable feed generation
- update tests helper to support no-content assertion
- update documention and usage files

With this commit the users will be able to generate NuGet config file
with unstable feed to support pre-release development - e.g. when updating
this generator :)
4502222
@peterblazejewicz peterblazejewicz added a commit that closed this issue Dec 1, 2015
@peterblazejewicz peterblazejewicz 🎨 Add unstable NuGet config option. Closes #183
- add conditional option to NuGet subgenerator
- update tests to cover unstable feed generation
- update tests helper to support no-content assertion
- update documention and usage files

With this commit the users will be able to generate NuGet config file
with unstable feed to support pre-release development - e.g. when updating
this generator :)
314fbce
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment