Bug 13939 - aspnetwebstack assemblies not found by Add References dialog
Summary: aspnetwebstack assemblies not found by Add References dialog
Status: RESOLVED DUPLICATE of bug 11004
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Project Model ()
Version: 4.0.12
Hardware: Macintosh Mac OS
: Low normal
Target Milestone: master
Assignee: Lluis Sanchez
URL:
Depends on:
Blocks:
 
Reported: 2013-08-12 23:18 UTC by Silvio
Modified: 2013-08-25 02:39 UTC (History)
1 user (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED DUPLICATE of bug 11004

Description Silvio 2013-08-12 23:18:10 UTC
Trying to create an ASP.NET project, using 4.5 profile, I'm not able to find any of the expected assemblies for Web API or MVC4. The aspnetwebstack pkg file is located in the default pkg-config path. I've even tried specifying the PKG_CONFIG_PATH env variable to point to the folder, but I still cannot find the appropriate assembiles. I've cleaned my system of mono, reinstalled both Xamarin Studio and Mono 3.2.1, but still nothing.
Comment 1 Mikayla Hutchinson [MSFT] 2013-08-25 02:39:27 UTC

*** This bug has been marked as a duplicate of bug 11004 ***