OpenAuth.Core | Authorization management | DevOps library

The title is quite self explanatory.

I spent a day working on this project, everything was fine until I tried to publish the changes for deployment. First I thought the issue was with the actual publishing but then I realised that the issue actually only happens when building the project in release mode.

The solution is made up of various projects. The main project is a .Net Framework Web Forms application. Most of the other projects are class libraries. The programming languages being used are all .NET based. The Main project is written in VB.Net, the referenced projects are a mixture of C# and VB.Net.

Originally the Main project was running in .Net Framework 4.6.2, and some other referenced projects were running in .Net Framework 4.6.0. Recently, we had an issue where we upgraded the referenced projects to 4.6.2 too.

In Debug I have no issues whatsoever. However, I suspect when the change in framework happened, something got messed up in the solution and caused the project to stop building in release mode.

The errors I am seeing are all related to ambiguity.

• 'CloudStorageAccount' is ambiguous in the namespace 'Microsoft.WindowsAzure.Storage'
• 'CloudFileClient' is ambiguous in the namespace 'Microsoft.Windows.Azure.Storage.File'
• 'CustomClassName' is ambiguous in the namespace 'ExternalClassLibrary.NamespaceName'

One must keep in mind that these same supposedly ambiguous classes work in Debug mode, meaning obviously the errors are incorrect. I’ve also made sure there are no duplicate CustomClassName/s. I also tried deleting the class names mentioned within the errors and re-creating them in different namespaces (since these cases are completely within our control). Nothing seems to make a difference.

I have tried to revert the Frameworks to the original versions (which were successfully building in release mode before) - this also made no difference whatsoever. Note that in debug mode, everything works regardless of framework version.

Tried looking into NuGet packages - restoring and re-installing some packages I suspected could be causing the issue; also to no avail.

The following is the list of NuGet packages as well as the file-based references from the project's .vbproj file. Had to remove some references which I thought are unlikely related to the issue, as the whole list exceeded the 30000 characters limit of StackOverflow questions. (These were DLLs that are built as part of any new project, and the rest of the DLLs that come bundled as part of DotNetOpenAuth library)

I've searched SO for similar questions and reviewed all of them but I haven't found one that helped me with the issue that I'm having.

I'm trying to add authentication to our legacy webforms application for Azure AD. Another developer already added OpenID support so I thought the easiest way to get this to work would be to use the OpenID endpoint in AzureAD and the exisiting code in our application. However, I have not been able to get it to work.

I don't know if the problem is in the endpoint URL that I'm using, the code we are using to try and connect, in how I have the AzureAD application configured, or a fundamental misunderstanding about what I'm trying to do.

This is supposed to be a multi-tenant application meaning, if I understood this properly, users can sign in with accounts in our Azure AD or other Azure ADs and then our application can choose to grant not grant access. But, I haven't even been able to get it to acknowledge that I'm targeting a valid OpenID endpoint much less even log in with a user from our own Azure AD.

The OpenID code is written using http://dotnetopenauth.net/ and the error occurs when we call CreateRequest()

This my web.config