xamarin/Xamarin.Forms

XmlnsDefinition generates false positive error on IDE

Open

#8,491 opened on Nov 13, 2019

View on GitHubContributor guide
 (4 comments) (0 reactions) (1 assignee)C# (1,926 forks)batch import
e/6 :clock6:feedback-tickethelp wantedinactivet/bug :bug:up-for-grabs

Repository metrics

Stars
 (5,644 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

This issue has been moved from a ticket on Developer Community.

When having a library that uses XmlnsDefinition to map namespaces to a single url, and use this one in another project in .xaml file, while it works and compiles fine, it generates an IDE Error saying “Value cannot be null.”. Building and running works great, but it is annoying to see errors while there aren’t.

Original Comments

Visual Studio Feedback System on 7/11/2019, 11:46 PM:

Greg Munn [MSFT] on 7/31/2019, 00:56 PM:

Dionysis Chasakis on 8/1/2019, 01:49 AM:

Greg Munn [MSFT] on 8/5/2019, 00:26 PM:

Dionysis Chasakis on 8/6/2019, 01:05 AM:

Visual Studio Feedback System on 8/9/2019, 08:10 AM:

Visual Studio Feedback System on 10/31/2019, 11:05 AM:

Original Solutions

(no solutions)

Contributor guide

Research direction
Investigate the XAML language service in Visual Studio for Mac to understand why XmlnsDefinition causes a false positive 'Value cannot be null' error. Trace the code path that validates XAML elements when x:Name is added to a view imported via XmlnsDefinition URL mapping.
Tech stack
csharp
Domain
mobile
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65