NullReferenceException under Windows 8

Stimulsoft Reports.NET discussion
Post Reply
ChrDressler
Posts: 68
Joined: Tue Nov 09, 2010 2:05 pm
Location: Dresden

NullReferenceException under Windows 8

Post by ChrDressler »

Hi,

I use V 2012.1 WPF successful under WinXP, Win7 (32, 64).
Under Window 8, I receive a NullReferenceException. :(
.Net FW4.0 Client is installed.
Your Designer.Wpf.exe runs correct. :?

What can I do?

-Christoph

System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
bei System.Windows.StyleHelper.GetInstanceValue(UncommonField`1 dataField, DependencyObject container, FrameworkElement feChild, FrameworkContentElement fceChild, Int32 childIndex, DependencyProperty dp, Int32 i, EffectiveValueEntry& entry)
bei System.Windows.StyleHelper.GetChildValueHelper(UncommonField`1 dataField, ItemStructList`1& valueLookupList, DependencyProperty dp, DependencyObject container, FrameworkObject child, Int32 childIndex, Boolean styleLookup, EffectiveValueEntry& entry, ValueLookupType& sourceType, FrameworkElementFactory templateRoot)
bei System.Windows.StyleHelper.GetChildValue(UncommonField`1 dataField, DependencyObject container, Int32 childIndex, FrameworkObject child, DependencyProperty dp, FrugalStructList`1& childRecordFromChildIndex, EffectiveValueEntry& entry, ValueLookupType& sourceType, FrameworkElementFactory templateRoot)
bei System.Windows.StyleHelper.GetValueFromStyleOrTemplate(FrameworkObject fo, DependencyProperty dp, EffectiveValueEntry& entry)
bei System.Windows.StyleHelper.ApplyStyleOrTemplateValue(FrameworkObject fo, DependencyProperty dp)
bei System.Windows.StyleHelper.InvalidateContainerDependents(DependencyObject container, FrugalStructList`1& exclusionContainerDependents, FrugalStructList`1& oldContainerDependents, FrugalStructList`1& newContainerDependents)
bei System.Windows.StyleHelper.DoStyleInvalidations(FrameworkElement fe, FrameworkContentElement fce, Style oldStyle, Style newStyle)
bei System.Windows.StyleHelper.UpdateStyleCache(FrameworkElement fe, FrameworkContentElement fce, Style oldStyle, Style newStyle, Style& styleCache)
bei System.Windows.FrameworkElement.OnStyleChanged(DependencyObject d, DependencyPropertyChangedEventArgs e)
bei System.Windows.DependencyObject.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
bei System.Windows.FrameworkElement.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
bei System.Windows.DependencyObject.NotifyPropertyChange(DependencyPropertyChangedEventArgs args)
bei System.Windows.DependencyObject.UpdateEffectiveValue(EntryIndex entryIndex, DependencyProperty dp, PropertyMetadata metadata, EffectiveValueEntry oldEntry, EffectiveValueEntry& newEntry, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType)
bei System.Windows.DependencyObject.InvalidateProperty(DependencyProperty dp, Boolean preserveCurrentValue)
bei System.Windows.FrameworkElement.UpdateStyleProperty()
bei System.Windows.FrameworkElement.OnInitialized(EventArgs e)
bei System.Windows.Controls.Menu.OnInitialized(EventArgs e)
bei System.Windows.FrameworkElement.TryFireInitialized()
bei System.Windows.FrameworkElement.EndInit()
bei System.Windows.Controls.ItemsControl.EndInit()
bei MS.Internal.Xaml.Runtime.ClrObjectRuntime.InitializationGuard(XamlType xamlType, Object obj, Boolean begin)
bei MS.Internal.Xaml.Runtime.PartialTrustTolerantRuntime.InitializationGuard(XamlType xamlType, Object obj, Boolean begin)
bei System.Xaml.XamlObjectWriter.Logic_EndInit(ObjectWriterContext ctx)
bei System.Xaml.XamlObjectWriter.WriteEndObject()
bei System.Xaml.XamlWriter.WriteNode(XamlReader reader)
bei System.Windows.Markup.WpfXamlLoader.TransformNodes(XamlReader xamlReader, XamlObjectWriter xamlWriter, Boolean onlyLoadOneNode, Boolean skipJournaledProperties, Boolean shouldPassLineNumberInfo, IXamlLineInfo xamlLineInfo, IXamlLineInfoConsumer xamlLineInfoConsumer, XamlContextStack`1 stack, IStyleConnector styleConnector)
bei System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
bei System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)
bei System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)
bei System.Windows.Application.LoadComponent(Object component, Uri resourceLocator)
bei Stimulsoft.Report.WpfDesign.StiWpfDesignerControl.InitializeComponent()
bei Stimulsoft.Report.WpfDesign.StiWpfDesignerControl..ctor(StiReport report, Boolean isRibbonGuiMode)
bei Stimulsoft.Report.WpfDesign.StiWpfDesigner..ctor(StiReport report)
bei Meduna.App.OnStartup(StartupEventArgs e)
Last edited by ChrDressler on Thu Apr 25, 2013 12:28 pm, edited 1 time in total.
Foxpro and behind
Alex K.
Posts: 6488
Joined: Thu Jul 29, 2010 2:37 am

Re: NullReferenceException under Windows 8

Post by Alex K. »

Hello,

We couldn't reproduce the issue.
Please check the last version.

Thank you.
ChrDressler
Posts: 68
Joined: Tue Nov 09, 2010 2:05 pm
Location: Dresden

Re: NullReferenceException under Windows 8

Post by ChrDressler »

Hi,

I can't check the last version, because I was I customer of you until 2012.1. I must deliver this version to my customers.
I have replaced he exception in the OP with a more detailed version.

I think there is a conflict between FW3.5 (Your Designer) and 4.0 (my App). If I write in the *.config for your Designer.Wpf.exe:
<startup>
<supportedRuntime version="v2.0.50727"/>
<supportedRuntime version="v4.0"/>
</startup>

it runs fine. If I exchange this both entrys, it crashs with the exception above.
My App is compiled for FW4.0, the *.config must have V4.0 an first! In other words:
How can I achieve, that Sti "finds" FW V3.5 and my App FW4.0?

-Christoph
Foxpro and behind
HighAley
Posts: 8430
Joined: Wed Jun 08, 2011 7:40 am
Location: Stimulsoft Office

Re: NullReferenceException under Windows 8

Post by HighAley »

Hello.

We transferred the Reports.Wpf product to .NET Framework 4.0. It will be good if you will upgrade to the latest release. Then there will be no conflict.

Thank you.
Post Reply