CSLA .NET

Vibrant discussion about CSLA .NET and using the framework to build great business applications.

Forum has moved

New location: CSLA .NET forum


CSLA .NET Resources:
  • CSLA .NET forum
  • CSLA .NET home page
  • Authentication issue

    rated by 0 users
    Answered (Verified) This post has 1 verified answer | 2 Replies | 1 Follower

    Not Ranked
    4 Posts
    poulin_julien posted on Tue, Nov 22 2011 11:05 AM

    I have a simple WPF application and recently upgraded from 4.1 to 4.2 and authentication didn't work anymore.

    I've compared the source between 4.1 and 4.2, and it seems related to the way the user it stored in the ApplicationContextManager. I'm performing authentication on a background thread to avoid freezing the UI and since the user is set to Thread.CurrentPrincipal, it gets lost in the process...

    Is there a workaround for this problem?

    Answered (Verified) Verified Answer

    Top 10 Contributor
    9,475 Posts
    Verified by poulin_julien

    A WPF application must reference Csla.Xaml.dll so the correct ApplicationContext.User provider is used. WPF requires special of the principal, and that special handling is implemented in a provider that is in that assembly.

    Rocky

    All Replies

    Top 10 Contributor
    9,475 Posts
    Verified by poulin_julien

    A WPF application must reference Csla.Xaml.dll so the correct ApplicationContext.User provider is used. WPF requires special of the principal, and that special handling is implemented in a provider that is in that assembly.

    Rocky

    Not Ranked
    4 Posts

    Thank you for your help.

    Page 1 of 1 (3 items) | RSS

    Copyright (c) 2006-2014 Marimer LLC. All rights reserved.
    Email admin@lhotka.net for support.
    Powered by Community Server (Non-Commercial Edition), by Telligent Systems