Thoughts from the Wet Coast
The musings of an ASP.NET Developer from Canada's We(s)t Coast
However, until recently I have been mainly involved writing “server-side” Visual Basic or C# code in the ASP.NET Web Forms model. In that model, when a user clicks a button (or hyperlink) on a web page or makes a selection in a drop-down control this invariably results in a post back to the server which responds to the client-side action, and then completely refreshes the page.
One of Reacts strengths is that it is NOT an MVC or MVVM framework. These frameworks can get quite slow when there are a lot of complex updates being made to the underlying models. The frameworks are continuously monitoring for changes and one change to one component can lead to hundreds or thousands of changes to other objects, and the frameworks are continuously updating the DOM to visualize the changes.
Last summer DNN Corp announced their intention to support MVC in future versions of the eponymous DNN Platform.
Last week Joe Brinkman announced that the initial fruits of those labours was now available in a CTP of DNN 7.5. The support introduced in 7.5 will allow developers to build their DNN modules using ASP.NET MVC version 5.1.1 or later.
Today, Scott Guthrie announced the new Microsoft Azure App Service. Azure App Service is a collection of 4 Application types– Web Apps, Mobile Apps, Logic Apps and API Apps.
Up until a few years ago, at DNN Corp we had primarily been using jQuery to do that manipulation. Don’t get me wrong jQuery is an awesome framework, but jQuery directly manipulates the DOM - there is no concept of working with models/objects in jQuery – i.e. separating your presentation aspects from your other logic.
Welcome to a new series on the latest version of ASP.NET – currently being called ASP.NET vNext (or ASP.NET 5). Microsoft has been working on this latest version of ASP.NET for just over a year and last month they released a Beta 1 preview of the code and tooling as part of the Visual Studio 2015 Preview.
In my investigation of the Neo4j database I will now turn my attention to the Neo4j browser.
Once Neo4j is installed there will be a small executable that can be used to start the Neo4j database server.
In this blog post I am going to return to my investigation of the graph database Neo4j. So far I have done a brief introduction to Neo 4j and I have shown how easy it is to install Neo 4j in an Azure VM.
In this DNN Development Tips series I have blogged quite a bit about testing. But how can we ensure our classes are testable?
The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.