Progressive .Net tutorials conference - last day

Today is last day for .Net conferences and here are some notes I took along the different talks. I hope you get something from it...

Why I'm not leaving .Net

Mark Rendle

Historical overview about the history of  .Net
c# name comes from c++++, taking all those pluses together and building the sharp symbol

c#6: string interpolation / asp.net dnx (shell: run clr on linux), (lot of stuff)
c#7: algebraic data-types / pattern matching / real tuples

ASP.NET5: How to get your cheese back

Tugberk Ugurlu

Cross platform development is one of the most important features revealed in the last BUILD conference from Microsoft.

In this new ASP .Net version you need to know exactly what are you doing when you deploy your web solutions because you have to create your Pipeline in IIS: all modules needed, configuration and so...

Compilation in memory is a new feature which makes the compilation process more fast. You will be able to hook directly with the compilation process. Even sharing my new compilation steps with other projects.

Dependency all the way down (customize with your own DI engine)

Change in the .csproj to .json project definition file

Going further with ASP.NET5

Tugberk Ugurlu

dnvm list: show all the frameworks installed and which is active
dnvm use "fr name": change active framework for current thread (cmd)
dnvm use "fr name" -p: same before but persist (every thread)
dnvm use "fr name"-r coreclr: using the coreclr
dnvm install "fr name" -u: last unstable version of a framework

dnu development utility: used for building publishing, restoring pckgs
where dnu: dnu runtime version tied

.json:
 - share: allows you to share wathever you want within your project. You'll be ending sharing .cs files with other people instead of the old nuget dll files.

Knowing what went bump in Production - modern monitoring in .Net

Chris O'Dell and Peter Mounce (JustEat)

Set of tools they work with to monitor in advance problems in production:

• Kibana
• Logstash
• Grafana

Introduction to RabbitMQ & EasyNetQ

Mike Hadlow @mikehadlow (blog: coderant.com)

Why messaging?

• Robust messaging for applications
• Easy to use
• Runs on all major operating systems
• Supports a huge number of developer platforms
• Open source and commercially supported

RabitMQ

• Message Broker
• Single point of management
• Erlang (clustering ootb)
• Multi-platform
• Owned by Pivotal
• AMQP
• Client libs for most languages

AMQP Exchange-Binding-Queuing
tryrabbitmq.com
Exchange / Producer / Queue / Consumer

With RabbitMQ you have to manage:

• Message patterns
• Connection management
• Serialization
• Channels
• Threading
• Error handling strategy

EasyNetQ
Handy framework for .Net to create your messaging solutions with RabbitMQ set underneath. It has several qualities like connection management which will open a new connection with consumers as soon as it goes down.