Could not load type 'Owin.IntegratedPipelineExtensions' from assembly 'Microsoft.Owin, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. - by Genius_kld

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 801735 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 9/20/2013 6:40:02 AM
Access Restriction Public


Could not load type 'Owin.IntegratedPipelineExtensions' from assembly 'Microsoft.Owin, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. 
Sign in to post a comment.
Posted by Microsoft on 9/30/2013 at 1:02 PM
The references in the repro project are wrong. Most of the references in the web project reference to non-existing location.
After fixing all the references pointing to the right location, I can't repro the issue.

Visual studio will fallback reference path to bin folder if he can find a dll with same name. I guess the issue is that your bin folder has some old version files and VS can still compile with them. Please manually remove bin folder in your web project before your next try.
Posted by Praburaj [MSFT] on 9/30/2013 at 12:33 PM
Thanks for submitting this feedback. Microsoft.Owin package underwent some re-factoring post preview based on feedback. The class 'IntegratedPipelineExtensions' which contains the UseStagemarker() extension was moved to the namespace Microsoft.Owin.Extensions based on feedback. The aspnet identity package (preview) - trying to use the UseStageMarker() - has a dependency on the preview version of Microsoft.Owin.

To resolve this issue try one of the following:
1. Update all the packages including the *aspnet.Identity* packages – You will still have to fix up any template code changes made in RC by yourself.
2.[Recommended]: Use VS 2013 RC to create projects. By this way you automatically get the template code changes done to accommodate katana changes as well as RC version of all packages.
Posted by Macy [MSFT] on 9/27/2013 at 2:34 AM
Thanks for your response. We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Genius_kld on 9/25/2013 at 6:30 AM
I posted the entire solution. The problem in the project InstaSmm - mvc application. Try to sign in or register. I tried the tips of community and stackoverflow, the situation still same.
Posted by Macy [MSFT] on 9/24/2013 at 7:04 PM
I am currently standing by for an update from you and would like to know how things are going on your end. If you could get back to me at your earliest convenience with information I request, we will be able to make headway towards a resolution. I look forward to hearing from you.
Posted by Macy [MSFT] on 9/23/2013 at 8:04 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please give us a demo project to demonstrate this issue so that we can conduct further research?

Please submit this information to us within 4 business days. We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Macy [MSFT] on 9/20/2013 at 6:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(