-
If you're looking to see if the object would have errors if it is in the other state, you could clone the object and then mark it as in the other state. After that you just check the rules on the clone, but it probably won't be that performant either.
-
Maybe use a Gate rule. See here for an example http://forums.lhotka.net/forums/p/9427/44686.aspx The gate rule could look for the exiting error, and change the error type if it matches.
-
There are two problems you have to solve. Using Mixed authentication (AD + FormsAuthentication) with ASP.Net. If you Google/Bing around, you'll find that this is a fairly common problem people run into with ASP.Net. You may find a more elegant solution than the one I described that deals better with your DMZ setup. Using a Custom CSLA principal
-
The method I described uses CslaAuthentication of CSLA in the main web.config with a custom Principal and Identity that are loaded in your main application from a FormsAuthentication cookie. The authentication portal is actually a separate application with the IIS security type set to Windows which just verifies the user's identity and sets the
-
You can create a separate authentication app that uses windows authentication to set a the FormsAuthentication cookie for your custom CSLA Priciple and Identity. The main app would redirect to the authentication portal to automatically set the cookie, but if the user cannot access the authentication portal it would have to direct them to a regular login
-
I'm trying to step through some CSLA authentication code and I would appreciate if the symbols for the Nuget packages could be published to symbolsource.org. The process is described in the Nuget documentation here http://docs.nuget.org/docs/creating-packages/creating-and-publishing-a-symbol-package and the setup on the developer's machine here
-
I created a room over at http://jabbr.net/#/rooms/CSLA for some real-time discussion if anyone is interested.
-
Great, I really miss the summaries for Intellisense when I'm coding. FYI: for the PDBs, you may want to check out this article from David Ebbo http://blog.davidebbo.com/2011/04/easy-way-to-publish-nuget-packages-with.html
-
Could you please include the documentation XML files in all the packages? Currently it only exists in the CSLA Core package with the "sl3-wp" project type. Thanks jaans! Releasing these through Nuget as it makes my life allot easier working on varied machines.