on the new ASP.NET 5. A lot of overlapping information. New features of visual
studio 2015. This session also confirms that WEB API is the way to go in the
Here is a summary
of the foundational improvements:
- New light-weight and modular
HTTP request pipeline
- Ability to host on IIS or
self-host in your own process
- Showed in the session, you can
host is from command line on USB stick.
- Built on .NET Core, which
supports true side-by-side app versioning
entirely as NuGet packages
- Not part of the System.Web.dll
- Integrated support for creating
and using NuGet packages
- Single aligned web stack for
Web UI and Web APIs
- Built-in support for dependency
- New tooling that simplifies
modern Web development
- Build and run cross-platform
ASP.NET apps on Windows, Mac and Linux
source and community focused
internet of your things (Iot)
about Azure and the capabilities to host applications on Azure. Interesting was
the table storage. You can create a table service where different types of data
can be stored in 1 table. It’s a no SQL datastore. This is ideal for storing
structured non relational data.
to live longer and happier with Visual Studio 2015
session was about the new features of Visual Studio 2015.
You can see
that a lot of resharper functionality is now default in VS 2015.
with a BOWER, Gulp and Grunt are used very frequenly. For packages like
AngularJS, bower is better than NuGet.
Who are You and What Have You Done With My ORM?
who gave the session is an expert on EF. She wrote books and gives trainings about
it. Her conclusion in regard with the silver bullet key note is that the best
way to go for the future is:
- Keep using EF 6.0 in existing
- Start using EF 7.0 in new projects.
EF7 is a
complete makeover of the entity framework. Since the start of EF they continued
on the same code base. For EF7 they restarted completely from the beginning, to
make it more light weight and also to tackle some challenges that were not
possible to take with the old code base.
once, run anywhere”: Can AngularJS & Cordova do it?
This was definitely
my favorite session. Christian Weyer explained in 1 hour and 30 min the
complete lifecycle of a modern app that has 1 code base but can be published in
He is co-owner
of thinktecture that tackle very large implementations
base is EF --> .Net WEB API --> AngularJS.
they can deploy the code to native iOS, Android and Windows Phone.
AngularJS is also available in any browser and can even be build to native Apps
for Windows and Mac OS.
alive!": Real-time applications with ASP.NET SignalR and AngularJS
great session by Christian Weyer. SignalR is definitely something to look into.
Very brief it’s a way to let the server communicate to the clients. E.g. when
some data is updated and the clients need to refresh without the user having to
click on a refresh button.
If setup the code in the correct way, you could prevent this.
The demo were not impressive, some failed. I do not believe in Aurelia, since
the community behind it is not comparable with AngularJS.
Driven Design for the Database Driven-Mind
view on application architecture. This looks promising, but at the moment not feasible
because lack of knowledge and high impact on development. Also we are in a
process of change that first need to be advanced.
Engaging User Experience & the Natural User Interface
about user experience. Not very interesting. Talking a lot about xbox Kinect and
Here is a
good summery made by one of the attendees:
probably safe to assume that you all know and use the Console Tab of Google
of the time we do that by using “console.log” statement which writes
your logging messages to the console. If you are using a lot of those “console.log”
statements in your code then things can quickly get messy and it will become
difficult to work through your logs to find the one line you actually need.
your statements you can use “console.groupCollapsed” and “console.groupEnd”.
These functions will create a collapsable group in the log window so you can
find your debug lines faster.
If you want
to measure how fast your code is executing you can use “console.time”
and “console.timeEnd”. This can also prove quite handy when you want to
benchmark certain functions.
Emulator enables you to test out your website on several devices (phones,
tablets, computers…) and on different network speeds (4G, 3G, GPRS…). This
makes it very easy to test out your responsive design. The emulator even
supports touch events!
enable/disable it by toggling the device icon in your Dev Tools.
tab is used to monitor the performance of your application and helps you
identify slow loading resources. It includes detailed timing data, HTTP request
and response headers, cookies…
useful feature of the Network tab is that you can download its contents to a
.HAR file. This could help us debug the “unreproducible bugs” reported by a QA
Engineer. If he’s doing his tests with the Network tab opened he can just send
the failed requests to a developer to investigate. All he has to do is
right-click the network table and select “Save as HAR with Content”.
This will download a .HAR-file that can be read using a tool called Chrome HAR Viewer.
inline editing just open up the console and type “document.body.contentEditable
= true” and press ENTER. You can now modify any text on your page by just
typing into the browser window. If you have to build a multilingual application
you can use this to easily test what would happen if the text in your title or
menu items would be translated (and thus be longer or shorter than intended by
the “sources tab”. Very often this tab includes a lot of scripts that
you don’t care about (external libraries etc.). You can prevent the debugger
from breaking in those scripts by “blackboxing” them. Just right-click
on the file and select “Blackbox Script”. You can stop blackboxing a
script by right-clicking the same file and selecting “stop blackboxing”.
You can add
CSS styling to your “console.log” statements. This can prove useful if
you want something to stand out if it occurs.
that this blogpost is just a high level overview of useful and time saving
features that were presented by Shay Friedman (@ironshay) at Techorama. The Google Chrome dev tools
contain a lot more functionality than what can be covered here. If you are
curious to learn more or want to read on about the topics covered in this post
you can visit https://developer.chrome.com/devtools.
This was an
interesting session that gave a deeper view of how the AngularJS binding works.
scratch (using code blocks and copy paste) that bound model to the view.
demo demo demo
This was a
replacing session were Julie showed EF 7 in combination with ASP.NET 5 in