Search This Blog

Playing with Visual Studio Online is sometime like playing with fire. It works great 99.99% of time, but from time to time you have a problem and you cannot find easily support.
In this post we will talk about what you need to do

when you want to add a new user and you end up with 401 or 403 error code.
This days we wanted to add a new user to our Visual Studio Online project. In the portal, when we wanted to add the new user we ended up with the following error:

"AAD guest users are not allowed to search in AAD"

This happens when we want to add a new user to a group. Even if we were administrators, we were not able to do any change. This was something new for us, 2 weeks ago everything was fine.
What happen in the last period of time. Our company integrated our own AD with Azure AD. To be able to use your administrator's rights on Visual Studio Online you need to be added to Azure AD (even if you have a LIVE account) as Member. By default you will be Guest.
PowerShell Command:

Comments

Post a Comment

Popular posts from this blog

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…

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:

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…