Skip to main content

ITCamp de vară în Cluj-Napoca, 18 August

For Romanian colleagues.
În luna August, ITCamp organizează un nou eveniment pentru profesioniștii IT din Cluj-Napoca. Evenimentul urmează să aibă loc pe data de 18 August, în clărirea Evozon.
Participarea la eveniment este gratuită. Mulțumim sponsorilor pentru sustinere (Evozon șiRecognos).
Program:
17:45 - 18:00 - Registration (coffee and beverages)
18:00 - 19:00 - .NET Security (Radu Vunvulea)
19:00 - 19:30 - Break (coffee and beverages)
19:30 - 20:30 - Actor based concurrency with Elixir (Adrian Magdas)
20:30 - 21:00 - Networking (coffee and beverages)

Descrierea sesiunilor:
.NET Security (Radu Vunvulea)
When is the last time when you pushed an update to .NET framework in a production environment? Did you defined an updated process of .NET framework for production environments? Is the support team aware about what can happen if a security update is not pushed to the machines?
In this session we will take a look on some security problems that .NET framework has and what can happen if we don't take security into account. We will take a look on different versions of .NET (including .NET Core). Best practives related to this topic will be covered and debated.
Actor based concurrency with Elixir
Because of increased demand for interconnected systems(IOT, SAAS) we need new improved ways of handling reliable (soft)real-time systems. One battle-tested approach is based on the Actor Model pioneered by Erlang and brought to the masses by Elixir.
Topics that will be covered:
- short introduction to functional programming principles with examples in Elixir
- actor model concurrency: why is it needed, advantages & disadvantages
- OTP patterns for handling agents: GenServer & Supervisor
Sponsori:
Evozone
Recognos

Comments

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…