An ASP.NET MVC 4 project for a Single Page Application (SPA) with Knockout for data binding, Durandal for composition and navigation, and Breeze for data management. (Works specifically for VS 2013 only)
The template is awesome but as another user stated, there are no updates to this module for MVC 5 or 6! This is one major reason why I refuse to use other people's independently built frameworks and extensions because of the lack of updates to keep current with the newest commercially available frameworks.
I will rate this template as a 5 star once you update it to work with the newest frameworks and it works just as good as your original version. Thanks!
Want to like this, but even as John Papa is getting paid partial revenue for his Pluralsight course in which the first three modules consist of John praising his own work here, the template is not being updated. ASP.NET MVC 5 is the current version of ASP.NET and ASP.NET MVC 6 is on its way.
After going through those first three modules that otherwise went nowhere and experiencing NuGet hell I gave up on the course and have a really bad taste in my mouth. No excuse for this.
Updating Bootstrap (id: Twitter.Bootstrap) to latest version (>3.0), Progress bar is not working..any quick resolution would be much appreciable. Progress bar stripes are not getting displayed as well as no color. I can see a box is being showed but something is breaking.
I have problems when attempting to publish to Windows Azure, using this Hot Towel Spa template for VS 2013. I get this error when I publish:
Error 4 Data at the root level is invalid. Line 1, position 1. C:\Users\dlabarca.VSI\Documents\Visual Studio 2013\Projects\Breadcrumb\WebRole.WebApp\Web.Release.config
Is there something to do to get around this issue?
@dlabarca, or anyone else who was having the error "Data at the root level is invalid. Line 1, position 1." while trying to publish to Azure. The problem is the encoding of the Web.Debug.config and Web.Release.config files. They start with an invisible character that needs to be deleted. I opened each one in Visual Studio 2013. you will notice that VS2014 adds a red squiggly on the line starting <?xml version="1.0">. Set the cursor before the very first character, click Delete once to delete the first "<" then Backspace to delete the invisible bad character, then retype the "<". The red squigglies should go away. Do this for both the Web.Debug.config and Web.Release.config files and you should be able to publish to Azure.
related post: http://stackoverflow.com/questions/291455/xml-data-at-root-level-is-invalid
@JohnPapa, I really like HotTowel and hope to see it upgraded to use MVC5! Thanks so much for posting this great template, and love your related Pluralsight videos!
I installed and run and I can see http://localhost:59391/#details type of urls
Can't believe that VS team still can't give us an SPA template with client side navigation and url parameters using history API!