问题
I've successfully used the EmberJS JavaScript framework with an ASP.NET web application, by referencing ember.js file.
I'm under the impression that Ember-CLI is the way Ember will be heading in future versions.
If this is correct, what's the appropriate way to keep using Ember going forward? Does it make sense to use Ember-CLI with ASP.NET, or is the assumption that the client is only ever static HTML and CSS/JS that calls back to server-side code (eg. WebAPI)?
回答1:
Ember-Cli is just the command line toolchain that the Ember community is "blessing", so it's really just a different way of building the ember app.
I'm actually using Ember-Cli with ASP.NET MVC and WebApi. Essentially what I'm doing is using EmberCLI to output an index.html file (ember new myapp sets up a project to do this by default), and then having my MVC app route to an /App url, where the controller returns a View("~/whateverdirectory/myapp/dist/index.html"); Razor doesn't care that the view you return isn't a .cshtml file, so this works fine, particularly if you're using Ember to control the whole page. This way you can use the standard authentication in ASP.NET, and then when the user is logged in, send them to the App controller's index route through MVC, and serve them the Ember app.
Update 8/18/2015
I've added some sample code on github.
来源：https://stackoverflow.com/questions/28619313/ember-cli-and-asp-net