Hey Everyone we’ve been hard at work updating ServiceStackVS to work with VS 2017 which includes converting all SPA templates completely over to webpack and integrating the latest features available in a modern SPA template.
Whilst all the SPA templates have been completed, we still have lots of docs to write since Webpack is pretty different from our previous JSPM-powered SPA templates, the main difference being Webpack is now responsible for bundling all web assets (e.g. js/ts/css/sass/html/img/fonts/etc) and will dynamically generate the optimal html based on your projects client deps. Each template includes an example of how to reference each asset. Webpack is now also responsible for compiling TypeScript instead of VS.NET so you’ll need to run the `00-webpack-watch` Gulp task in VS’s Task Runner Explorer which will watch any modified files and automatically transpile them so you still just need to refresh after the saving the file to see the changes. The other Gulp tasks still provide all the features from the previous SPA templates but they mostly just delegate to running npm scripts that are now being powered by webpack, so you’ve still got access to all the templates features from within VS.NET’s Gulp Task Runner Explorer or if you prefer you can run the npm scripts from the command-line with `npm run {script-name}`.
I know a lot of you are keen on creating ServiceStack templates in VS2017 so if you want to access them before the next ServiceStack release you can download and install it directly from the link below:
https://s3.amazonaws.com/ci-dist/ssvs/latest/ServiceStackVS.vsix
If you’re on VS2015 and want access to the latest SPA templates you’ll need to go to Tools > Extensions and uninstall the existing SSVS Extension before installing the above VSIX.
If you run into any issues please report them to: https://github.com/ServiceStack/Issues
Enjoy!