Skip to main content

Where is the Add STS reference option in Visual Studio 2012?

In Visual Studio 2012 the Add STS reference… option is replaced by a completely new tool: The Identity and Access Tool.

The Identity and Access Tool for Visual Studio 2012 enables you to secure your application with claims based identity and accept users from multiple identity providers.

This extension adds a context sensitive project menu entry to easily add identity capabilities to your Web Applications, MVC Applications and WCF Services. This will provide you with capabilities for developing and testing your application with a Local Development STS, connecting to a corporate identity provider like ADFS2 and using the Windows Azure Access Control Service to connect to other identity provides such as LiveID, Google, Yahoo and Facebook. It does this by updating your web.config file with the proper settings to enable the Windows Identity Foundation in .NET 4.5 and adding the necessary configuration for the identity provider you select.

This tool is not available out-of-the-box. So you have to install it from the Extension Manager in Visual Studio:

    • From the menu select TOOLS | Extensions and Updates. . .
    • Click the Online extensions node in the tree view on the left.
    • Search for “Identity and Access Tool” in the search field in the upper right
    • Click the Download button to download and install the package.
    • Click Restart Now to Restart Visual Studio.

    After restarting Visual Studio, you should now see the Identity and Access. . . option if you right-click on your project.

    IdentityAndAccessTool

    Remark: If the option is not there after installing the extension, check if the target framework for your project is set to .NET 4.5.  I first tried it on a .NET 4.0 project and lost a lot of time investigating why the option was not available.

    Labels:

    Popular posts from this blog

    Azure DevOps/ GitHub emoji

    I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
    Read more

    Kubernetes–Limit your environmental impact

    Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
    Read more

    Podman– Command execution failed with exit code 125

    After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
    Read more