InfoStrat kills Intellisense in xaml (VS2010) + Reflection issues

Jul 15, 2010 at 1:14 PM

Hi @ll,

I have some serious trouble using InfoStrat in VS2010. First of I had to modify the app.config due to the mixture assembly problems. Now it is possible to use the dll in xaml, but as soon as I add the namespace intellisense in xaml is not running anymore - neither for standard wpf elements, attributs or the new elements from the reference.
Even more, every now an then my designer crashes and shows me reflextion issues:

System.Reflection.Adds.UnresolvedAssemblyException
Type universe cannot resolve assembly: Microsoft.MapPoint.Rendering3D, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35.
   at System.Reflection.Adds.AssemblyProxy.GetResolvedAssembly()
   at System.Reflection.Adds.AssemblyProxy.GetHashCode()
   at Microsoft.Windows.Design.Metadata.ReflectionMetadataContext.Reflectable`1.GetHashCode()
   at System.Collections.Generic.GenericEqualityComparer`1.GetHashCode(T obj)
   at System.Collections.Generic.HashSet`1.InternalGetHashCode(T item)
   at System.Collections.Generic.HashSet`1.Contains(T item)
   at Microsoft.Windows.Design.Metadata.ReflectionMetadataContext.CanParentContextSupportType(Reflectable`1 type)
   at Microsoft.Windows.Design.Metadata.ReflectionMetadataContext.GetTypeForReflectableType(Reflectable`1 reflectableType)
   at MS.Internal.Metadata.ClrType.GetTypeMetadata(Type type)
   at MS.Internal.Metadata.ClrType.get_BaseType()
   at MS.Internal.Design.Metadata.Xaml.XamlType.d__7.MoveNext()
   at MS.Internal.Design.Metadata.Xaml.XamlType.d__0.MoveNext()
   at Microsoft.Windows.Design.Metadata.Xaml.XamlExtensionImplementations.d__7.MoveNext()
   at MS.Internal.VirtualModel.VirtualModelPropertyCollection.d__0.MoveNext()
   at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
   at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
   at MS.Internal.VirtualModel.VirtualModelPropertyCollection.GetEnumerator()
   at MS.Internal.VirtualModel.VirtualModelUtilities.WrapProperties(IVirtualModelItem item)
   at MS.Internal.VirtualModel.VirtualModelItem.System.ComponentModel.ICustomTypeDescriptor.GetProperties()
   at System.ComponentModel.TypeDescriptor.MergedTypeDescriptor.System.ComponentModel.ICustomTypeDescriptor.GetProperties()
   at System.ComponentModel.TypeDescriptor.GetPropertiesImpl(Object component, Attribute[] attributes, Boolean noCustomTypeDesc, Boolean noAttributes)
   at System.Windows.PropertyPath.ResolvePropertyName(String name, Object item, Type ownerType, Object context, Boolean throwOnError)
   at MS.Internal.Data.PropertyPathWorker.GetInfo(Int32 k, Object item, SourceValueState& svs)
   at MS.Internal.Data.PropertyPathWorker.ReplaceItem(Int32 k, Object newO, Object parent)
   at MS.Internal.Data.PropertyPathWorker.UpdateSourceValueState(Int32 k, ICollectionView collectionView, Object newValue, Boolean isASubPropertyChange)
   at MS.Internal.Data.ClrBindingWorker.AttachDataItem()
   at System.Windows.Data.BindingExpression.Activate(Object item)
   at System.Windows.Data.BindingExpression.AttachToContext(AttachAttempt attempt)
   at System.Windows.Data.BindingExpression.AttachOverride(DependencyObject target, DependencyProperty dp)
   at System.Windows.Data.BindingExpressionBase.Attach(DependencyObject target, DependencyProperty dp)
   at System.Windows.Data.BindingExpressionBase.OnAttach(DependencyObject d, DependencyProperty dp)
   at System.Windows.DependencyObject.SetValueCommon(DependencyProperty dp, Object value, PropertyMetadata metadata, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType, Boolean isInternal)
   at System.Windows.DependencyObject.SetValue(DependencyProperty dp, Object value)
   at System.Windows.Data.BindingOperations.SetBinding(DependencyObject target, DependencyProperty dp, BindingBase binding)
   at System.Windows.FrameworkElement.SetBinding(DependencyProperty dp, BindingBase binding)
   at MS.Internal.GridControl.GridChildMarginAdorner.SetDragBinding(ModelItem source, Boolean dragging)
   at MS.Internal.GridControl.GridChildMarginAdornerProvider.ChildMarginAdornerPanel.CalcLayout(Boolean measure)
   at MS.Internal.GridControl.GridChildMarginAdornerProvider.ChildMarginAdornerPanel.MeasureOverride(Size availableSize)
   at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
   at System.Windows.UIElement.Measure(Size availableSize)
   at MS.Internal.Interaction.BaseAdornerLayout.Measure(UIElement adorner, Size constraint)
   at MS.Internal.Interaction.AdornerLayer.MeasureOverride(Size constraint)
   at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
   at System.Windows.UIElement.Measure(Size availableSize)
   at System.Windows.ContextLayoutManager.UpdateLayout()
   at System.Windows.ContextLayoutManager.UpdateLayoutCallback(Object arg)
   at System.Windows.Media.MediaContext.InvokeOnRenderCallback.DoWork()
   at System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks()
   at System.Windows.Media.MediaContext.RenderMessageHandlerCore(Object resizedCompositionTarget)
   at System.Windows.Media.MediaContext.RenderMessageHandler(Object resizedCompositionTarget)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)

Strangely, compiling is ok and the app runs.

Any ideas how to solve this?

Thx in advance!

Coordinator
Jul 19, 2010 at 10:50 PM

I haven't seen those problems before. Perhaps you can try a repair install of Visual Studio.

Dec 28, 2010 at 6:23 PM

I can confirm that I experience exactly the same problem. I get the identical error in the WPF designer of VS 2010, but it all runs fine.

Would much appreciate if you could look into this please.

Coordinator
Jan 13, 2011 at 12:55 AM

alexreg:

I'm sorry but I have not come across this problem so I cannot attempt to fix it.

I'll say that in my Visual Studio 2010, I have the XAML editor set to load XAML only by default. (Tools | Options | Text Editor | XAML | Miscellaneous | Check "Always open documents in full XAML view") It loads quicker and doesn't have crash errors if a component is faulty. Regardless when I use the design it doesn't crash and I still have intellisense.