Bug 4278 - ASP.NET source editor should use proper project contexts
Summary: ASP.NET source editor should use proper project contexts
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: ASP.Net ()
Version: Trunk
Hardware: PC Mac OS
: Low normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-04-05 19:19 UTC by Mikayla Hutchinson [MSFT]
Modified: 2017-08-22 21:05 UTC (History)
2 users (show)

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:

Description Mikayla Hutchinson [MSFT] 2012-04-05 19:19:12 UTC
The ASP.NET source editor needs a project project context for resolving types in code completion to pass to the C# completion engine.

This should include a reference to:
* default system assemblies
* assemblies registered in the web.config
* assemblies registered in directives
* the project, if the aspx is bound to a project

This will update it to work correctly in newresolver.
Comment 1 Will Smith 2017-08-22 21:05:23 UTC
Thanks so much for taking the time to submit this report! I attempted to reproduce this issue based on the bug description with the latest Visual Studio 2017 for Mac Preview version 7.2, and I was unable to hit the problem. If this issue is still occurring for you, please reopen this report and attach a reproduction, ideally starting with a new template project and then adding just the code necessary to demonstrate the issue.