Update to avoid using .remote() about generator-aspnet HOT 7 CLOSED

We have all of the templates local to the generator for subgenerators, what is everyone's thought?

from generator-aspnet.

If possible I think generator-asponet should use built-in copy feature of Yo's.

There is two level built-in solution in Yeoman to update generators AFAIK and keep users up-to-date with released, most recent versions:

#1
if user run yo she will be presented with option to update installed generators:

  Mocha 
  ──────────────
❯ Update your generators 
  Install a generator 

update:
generator-aspnet update is presented that way:

? 'Allo Piotr! What would you like to do? 
  ──────────────
  Run a generator
  Angular 
❯ Aspnet ♥ Update Available! 
  Bootstrap 
  Bootstrap Examples 
  Generator 
(Move up and down to reveal more choices)

#2
if generator-aspnet adds Yeoman's update plugin dependency the status of generator-aspnet will be checked on each run by Yeoman's itself:
https://github.com/yeoman/update-notifier

There is additional benefit of moving to use copy feature instead of fetching from git directly. During generator development that is not possible to work with locally updated content - samples are always fetched from remote upstream master - not from local repository used for development.

from generator-aspnet.

Yes I agree we should stop using .remote(). I think having all the files in the npm package is better so that offline works and so that you don't have to push to github to test template changes.

Update plugin sounds good as well.

from generator-aspnet.

The implementation for local templates/files can be as simple as:
https://gist.github.com/peterblazejewicz/9ae54b300b862b4e5320
I'd also think about bringing back tests for templ/files creation process.

from generator-aspnet.

@peterblazejewicz have you done this locally and tested?

from generator-aspnet.

@spboyer Yes, this is from my local branch. Can I bring back default Yeoman's testing structure to project? (by default yeoman-generator scaffolds tests for generator projects). I could investigate this.
I would not add local copy features yet unless covered by tests

from generator-aspnet.

.remote() removed and test coverage added for entire repo in latest PR -> #59

from generator-aspnet.