Addy Osmani:
http://addyosmani.com/resources/essentialjsdesignpatterns/book/#detailnamespacing
Donnerstag, 6. März 2014
Mittwoch, 5. März 2014
Quote: Script Loader RequireJS and curl.js
Addy Osmani:
"There are a number of great loaders for handling module loading in the AMD and CommonJS formats, but my personal preferences are RequireJS and curl.js. Complete tutorials on these tools are outside the scope of this book, but I can recommend reading John Hann's article about curl.js and James Burke's RequireJS API documentation for more."
http://msdn.microsoft.com/en-us/magazine/hh227261.aspx
Source: http://addyosmani.com/resources/essentialjsdesignpatterns/book/#modularjavascript
"There are a number of great loaders for handling module loading in the AMD and CommonJS formats, but my personal preferences are RequireJS and curl.js. Complete tutorials on these tools are outside the scope of this book, but I can recommend reading John Hann's article about curl.js and James Burke's RequireJS API documentation for more."
http://msdn.microsoft.com/en-us/magazine/hh227261.aspx
Source: http://addyosmani.com/resources/essentialjsdesignpatterns/book/#modularjavascript
Quote: Developers fall back on variations of the module or object literal
Addy Osmani:
"Unlike some more traditional programming languages however, the current iteration of JavaScript (ECMA-262) doesn't provide developers with the means to import such modules of code in a clean, organized manner. It's one of the concerns with specifications that haven't required great thought until more recent years where the need for more organized JavaScript applications became apparent.
Instead, developers at present are left to fall back on variations of the module or object literal patterns, which we covered earlier in the book. With many of these, module scripts are strung together in the DOM with namespaces being described by a single global object where it's still possible to incur naming collisions in our architecture. There's also no clean way to handle dependency management without some manual effort or third party tools."
Quote: backbone.js vs. knockout.js
Addy Osmani:
"To conclude, I personally find KnockoutJS more suitable for smaller applications whilst Backbone’s feature set really shines when building anything non-trivial. That said, many developers have used both frameworks to write applications of varying complexity and I recommend trying out both at a smaller scale before making a decision on which might work best for your Project."
Source: http://addyosmani.com/resources/essentialjsdesignpatterns/book/#detailmvvm
"To conclude, I personally find KnockoutJS more suitable for smaller applications whilst Backbone’s feature set really shines when building anything non-trivial. That said, many developers have used both frameworks to write applications of varying complexity and I recommend trying out both at a smaller scale before making a decision on which might work best for your Project."
Source: http://addyosmani.com/resources/essentialjsdesignpatterns/book/#detailmvvm
Montag, 3. März 2014
Template JS: No .prototype - signature found in VS2013 SPA template
A check against the so called constructor pattern results in no ".prototype" hits concerning the VS2013 SPA template JS codebase.
Samstag, 1. März 2014
WebDeploy: Successfully registered and logged in a new user using VS2013 SPA template with local IIS 7.x
1. Try a Login with user: demo and password: demodemo
2. Register with user:demo and password: demodemo
3. Displaying the Home welcome page after logged in successfully
4. Showing the data Schema with some user data that was entered automatically during registering process
WebDeploy: Now working with local IIS 7.x on root deployment
Actually there still exists a Problem - for me - to get a proper solution working with a URL that directs to a IIS subfolder. This problem is currently addressed solely to forementioned "UNKNOWN ERROR OCCURED" error, when a user sends a request to http://localhost/VS2013SPATemplateOriginal.
I did a simple workaround then. Deploying the whole stuff to the IIS root folder "Default Websites" the VS2013 SPA template works properly. A user sends a request by entering http://localhost and the stuff is up and running as expected.
Therefore I will skip further investigations and proceed examining the VS2013 SPA template en detail from now.
Working steps for web deployment by using VS2013 Publishing functionality:
1. Publishing Connection
2. Publishing settings
...and the Folder structure within IIS 7.x
...and the folder structure on disk by Windows Explorer
...and the output by Visual Studio during publishing that ends successfully:
1>------ Erstellen gestartet: Projekt: VS2013SPATemplateDemo, Konfiguration: Release Any CPU ------
1> VS2013SPATemplateDemo -> C:\Daten\Projekte\VS2013\WebApp\VS2013SPATemplateDemo\VS2013SPATemplateDemo\bin\VS2013SPATemplateDemo.dll
2>------ Veröffentlichungsvorgang gestartet: Projekt: VS2013SPATemplateDemo, Konfiguration: Release Any CPU ------
2>"Web.config" wurde mithilfe von "C:\Daten\Projekte\VS2013\WebApp\VS2013SPATemplateDemo\VS2013SPATemplateDemo\Web.Release.config" in "obj\Release\TransformWebConfig\transformed\Web.config" transformiert.
2>Alle Dateien werden in das unten genannte temporäre Verzeichnis zum Packen/Veröffentlichen kopiert:
2>obj\Release\AspnetCompileMerge\Source.
2>C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_compiler.exe -v / -p C:\Daten\Projekte\VS2013\WebApp\VS2013SPATemplateDemo\VS2013SPATemplateDemo\obj\Release\AspnetCompileMerge\Source -u C:\Daten\Projekte\VS2013\WebApp\VS2013SPATemplateDemo\VS2013SPATemplateDemo\obj\Release\AspnetCompileMerge\TempBuildDir
2>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web\Deploy\Microsoft.Web.Publishing.MSDeploy.Common.targets(55,5): Warnung : Die angegebene DACPAC-Datei ist bereits vorhanden und wird überschrieben.
2>MSDeploy.dbDacFx (MSDeploy.dbDacFx) wird hinzugefügt.
2>Die Datenbank (C:\Daten\Projekte\VS2013\WebApp\VS2013SPATemplateDemo\VS2013SPATemplateDemo\obj\Release\AutoScripts\DefaultConnection_IncrementalSchemaOnly.dacpac) wird hinzugefügt.
2>Die automatische "ConnectionString" hat "obj\Release\AspnetCompileMerge\TempBuildDir\Areas\HelpPage\Views\Web.config" in "obj\Release\CSAutoParameterize\transformed\Areas\HelpPage\Views\Web.config" transformiert.
2>Die automatische "ConnectionString" hat "obj\Release\AspnetCompileMerge\TempBuildDir\Views\Web.config" in "obj\Release\CSAutoParameterize\transformed\Views\Web.config" transformiert.
2>Die automatische "ConnectionString" hat "obj\Release\AspnetCompileMerge\TempBuildDir\Web.config" in "obj\Release\CSAutoParameterize\transformed\Web.config" transformiert.
2>Alle Dateien werden in das unten genannte temporäre Verzeichnis zum Packen/Veröffentlichen kopiert:
2>obj\Release\Package\PackageTmp.
2>sitemanifest (sitemanifest) wird hinzugefügt.
2>Die Datenbank (data source=.\SQLExpress;initial catalog=VS2013SPATemplateDemoOriginalDB;integrated security=True;connect timeout=30) wird hinzugefügt.
2>Die Datei (Default Web Site\bin\App_global.asax.compiled) wird aktualisiert.
2>Die Datei (Default Web Site\bin\App_global.asax.dll) wird aktualisiert.
2>Die Datei (Default Web Site\PrecompiledApp.config) wird aktualisiert.
2>ACLs für den Pfad (Default Web Site) werden hinzugefügt.
2>ACLs für den Pfad (Default Web Site) werden hinzugefügt.
2>Die Veröffentlichung war erfolgreich.
2>Die Website wurde erfolgreich veröffentlicht http://localhost/
========== Erstellen: 1 erfolgreich, 0 fehlerhaft, 0 aktuell, 0 übersprungen ==========
========== Veröffentlichung: 1 erfolgreich, 0 Fehler, 0 übersprungen ==========
UnknownError: Hosting the VS2013 SPA template not in IIS root but subfolder
After deploying the VS2013 SPA template application including performed database schema changes the login resp. register form shows "unknown error occured" or "Unbekannter Fehler".
Because the deployment process was successful I tried then to dissect this issue:
Abonnieren
Posts (Atom)