Quantcast
Channel: Visual Studio General Questions forum
Viewing all articles
Browse latest Browse all 21115

Intellisense prblem in xaml codes with detecting classes in a given namespace in VS2013

$
0
0

I am having a Win8 store app and developing VS2013. Frequently, I face problem with intellisense trying to detect the classes in the referenced projects.

Let say I have a UserControl similar to this:

<UserControl x:Class="MyNamespace.MyControl" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:local="using:MyNamespace" xmlns:d="http://schemas.microsoft.com/expression/blend/2008" xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:ViewModels="using:MyNamespace.ViewModels" xmlns:Converters="using:MyNamespace.ViewModels.ValueConverters" mc:Ignorable="d" d:DesignHeight="300" d:DesignWidth="600" FontFamily="Global User Interface"><UserControl.Resources><Converters:MyConverter x:Key="MyConverter"/></UserControl.Resources><d:UserControl.DataContext><ViewModels:MyViewModel /></d:UserControl.DataContext>
...

When I open the control in the Designer of VS, the intellisense gives the following error:

The name "MyConverter" does not exist in the namespace "using:MyNamespace.ViewModels.ValueConverters".

I have to note that all projects are build successfully and the control works at runtime. Also classes "MyConverter" and "MyViewModel" belong to a referenced project. The other point that I have to mention is that namespaces "MyNamespace.ViewModels" and "MyNamespace.ViewModels.ValueConverters" are shared across some projects and based on the intellisense it seems that it only searches one assembly and not all referenced assemblies having those namespaces. For example if I have these namespaces inside my Win8 store app project, intellisense does not search in the referenced assemblies otherwise if it finds it in one of the referenced ones, it does not search through other referred assemblies. As a result the designer does not show the control at all and gives "Invalid Markup" error.



Viewing all articles
Browse latest Browse all 21115

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>