Remove dependent references of DotNetOpenAuth to build for web deploy

Question

0.00/5 (No votes)

See more:

, +

Hello all. I started a big project from a template, so it came with openauth by default. I chose to use Active Directory as my authentication scheme, so I had disabled openauth, removed the pages, and any references (including service references and references via nuget). Right now though, I cannot build for my publish because I get this error:

Copying file bin\DotNetOpenAuth.AspNet.dll to obj\Release\Package\PackageTmp\bin\DotNetOpenAuth.AspNet.dll failed. Could not find file 'bin\DotNetOpenAuth.AspNet.dll'.

Things I've tried:
-"Searching" for any references like oauth, openauth
-Re-installing and uninstalling via Nuget PM Console (still fighting a remaining self-dependency issue that won't let me get rid of the core because the core depends on it [WTFLOLGTFO?])
-Deleting the bin and obj folders, cleaning the solution, rebuilding and building the project.
-Giving Visual Studio what it wants. Didn't end well. Started asking for micro, integrated dependencies to OpenAuth such as mono.math.dll and mono.math.xml despite having nearly every possible reference to OpenAuth installed.

I have no idea where or why it's looking for the service reference which doesn't exist, and hasn't for quite some time.

Posted 29-Jan-14 6:35am

dfarr1

Add a Solution

Comments

ZurdoDev 29-Jan-14 15:04pm

Did you look at the References folder in Solution Explorer under your project?

dfarr1 29-Jan-14 15:06pm

Yes, all the dotnetauth/oauth references have been removed from that list.

ZurdoDev 29-Jan-14 15:20pm

Looked in project properties? Make sure there are no post build events.

dfarr1 29-Jan-14 15:27pm

That was clean as well. I might have found it - Visual Studio keeps it's own tabs on directory contents listing of the bin and obj folders where after looking at it from the VS side, the files that kept causing errors were all flagged with warnings as having potentially missing items. I deleted the folders from the actual directory and not through VS, so it's possible that VS kept trying to reference them because it didn't know I messed with those folders outside the application. It looks to be compiling now but I'll post back to verify whether that was it.

ZurdoDev 29-Jan-14 15:28pm

Interesting. If that's it, post as solution so this no longer shows as unanswered.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

dfarr1 · Accepted Answer · 2014-04-02T13:43:00

Visual Studio keeps it's own tabs on directory contents listing of the bin and obj folders where after looking at it from the VS side, the files that kept causing errors were all flagged with warnings as having potentially missing items. I deleted the folders from the actual directory and not through VS, so it's possible that VS kept trying to reference them because it didn't know I messed with those folders outside the application. It looks to be compiling now but I'll post back to verify whether that was it.