Error when startup WPF Application with Crystal Report !

Question

Hi!
I have an error when build & run a WPF Application with Crystal Report. Can anyone help me ?
First, I created 2 project, one is the WPF Application & one is Shell Start Up project (to show loading screen, then show main window when loaded, is WPF Application too)
WPF Application:
/// <summary>
    /// Interaction logic for MainWindow.xaml
    /// </summary>
    public partial class MainWindow : Window {
        public MainWindow() {
            InitializeComponent();
           // crViewer is SAPBusinessObjects.WPF.Viewer.CrystalReportsViewer
            crViewer.ViewerCore.ReportSource = new CrystalReport1(); // Assign report to viewer
Shell Startup:
[STAThread]
        public static void Main(string[] args) {
            AppDomain.CurrentDomain.UnhandledException += new UnhandledExceptionEventHandler(CurrentDomain_UnhandledException);
            Application app = new Application();
            ShowLoadingWindow(); // Show loading screen
            MainWindow mw = new MainWindow();
            mw.Show();
            app.Run();   
        static void CurrentDomain_UnhandledException(object sender, UnhandledExceptionEventArgs e) {
            // Exception was throw here
And here is the exception & it's stack trace
Message:  Object reference not set to an instance of an object.
Stacktrace:
at SAPBusinessObjects.WPF.Viewer.ViewerCore.<>c__DisplayClass1.<set_ReportSource>b__0()
   at SAPBusinessObjects.WPF.Viewer.DelegateMarshaler.<>c__DisplayClass29.<QueueOnThreadPoolThread>b__28(Object )
   at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

Answer 1

As far as I know the error is typically due to the fact that I'm trying to address an object that has not been set. E.g.; this could be due to  bad scoping, bad inits/constructs, trying to access a member of a class without instance object and so on. I suspect this is a design \ code issue. You might be able to confirm this using [Process Monitor|http://technet.microsoft.com/en-ca/sysinternals/bb896645.aspx].
Other than that, I'd recommend creating a phone case here:
http://store.businessobjects.com/store/bobjamer/en_US/pd/productID.98078100?resid=S6I@hgoHAkEAAGsiyVkAAAAR&rests=1282226845369
- Ludek