Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[VS] ASPX: Guests incorrectly see errors for valid types, classes, and namespaces #70

Closed
Chuxel opened this issue Jan 31, 2018 · 1 comment

Comments

@Chuxel
Copy link
Member

Chuxel commented Jan 31, 2018

While ASPX does not have deep intellisense support in VS Code, Visual Studio does. Unfortunately, right now ASPX's backing implementation for inline C# does not work with VS Live Share and this is a full feature needed to implement. This is was tagged as a bug given it's behavior, but it is effectively a full feature that is not currently supported.

Product and Version: Visual Studio 2017 Preview (15.6 Preview 3)
OS Version: Windows 10 Enterprise 64-bit
Live Share Extension Version: 0.2.58
Target Platform or Language: ASPX files in ASP.NET Web Forms projects

Steps to Reproduce / Scenario:

  1. [Host] Create a new ASP.NET Web Forms Site project
  2. [Host] Open Contact.aspx
  3. [Host] Share
  4. [Guest] Join
  5. [Guest] Look at Contact.aspx

Expected: No errors visible

Actual: Page.Title and Scripts show errors (red squiggles). Other incorrect warnings are also visible. Site.master.cs is a valid CodeFile and has a green squiggle under it and webopt is a valid prefix and also has a green squiggle.

Similar to #64 for F# and previously #51 for CSHTML.

@Chuxel Chuxel changed the title [VS] ASPX: Guests incorrectly see errors for valid types, classes, and namespaces in the code-behind [VS] ASPX: Guests incorrectly see errors for valid types, classes, and namespaces Jan 31, 2018
@Chuxel
Copy link
Member Author

Chuxel commented May 7, 2018

There should not be any "red squiggles" anymore as of v0.3.392/v.0.393. However full intellisense is not supported yet. Keep an eye on platform support for info on when we get this up and running.

@Chuxel Chuxel closed this as completed May 7, 2018
Chuxel added a commit that referenced this issue May 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant