-
Hi I am using a PropertyStatus control. When there is a single broken rule it works well. When there are multiple broken rules, the output of the control on the screen is not formatted properly. All of the error description strings are displayed but they are not justified properly. Can anyone point me to an example of xaml code to format the output
-
Hi Jonny, I tested again on my dev machine with CSLA 4.2 on both IIS and IIS Express and was unable to reproduce the problem. However the test was still failing on our build machine. I then installed the latest build of CSLA 4.2 on the build machine and the problem went away. The only possibility I can think of is that maybe the build machine had an
-
Hi Jonny, Yes we are using the CSLA background worker on the server side. I had a look at the ApplicationContext code in CSLA 4.2 as you suggested. I switched my app over to CSLA 4.2 and the problem went away when running under Cassini. However when I deployed my app to IIS the problem was still present. I am investigating further and will let you know
-
Hi Jonny, I am using Csla.Threading.BackgroundWorker, not System.ComponentModel.BackgroundWorker. After some more investigation I found that the ApplicationContextManager is starting out as a Csla.Web.ApplicationContextManager, but it is later switching to a Csla.ApplicationContextManager. This happens because the HttpContext.Current becomes null. If
-
Hi, I am having a problem with the ClientContext. I am using CSLA 4.1.0 for Silverlight. I've had this problem before and I thought I fixed it but it keeps coming back. It is a problem with the async DataPortal. I believe the problem occurs when there is more than one simultaneous call to the DataPortal - for example when multiple Silverlight ViewModels
-
Doh! its OK Jonny I found my problem, I had some code that I thought was executing on the server and it was executing on the client. Reading this post also helped me. http://forums.lhotka.net/forums/p/9153/43477.aspx Thanks.
-
Hi Jonny, Thanks for your reply. I understand that the ClientContext is passed only from the Client to the Server with each DataPortal call, and is not passed back. I am not adding anything to the ClientContext on the server side. On the client side I set up the ClientContext at startup. On the client side I verify (with an Assert) that the Context
-
Hi, I am using CSLA 4.1.0 for a Silverlight app. I recently experienced a problem where my ClientContext was being randomly cleared. After a lot of digging I have traced the source of the problem (I hope). It is because I am refreshing several ViewModel objects simultaneously. I am using the MVVM pattern. I have a main page user control with several
-
Thanks heaps Rocky. That fixed it. I included the code change below. protected override void OnDeserialized() { base.OnDeserialized(); this.ChildChanged +=MetadataGroupTreeNodeList_ChildChanged; } private void MetadataGroupTreeNodeList_ChildChanged(object sender, ChildChangedEventArgs e) { var child = e.ChildObject as MetadataItemTreeNode; if (child
-
Hi, we are developing a silverlight 3 tier app using CSLA 4.1.0. We have been working on it for about 3 months now and have found CSLA to be a great help. I have a problem with LinqObservableCollection. I have a business object class that inherits BusinessBase, called MetadataGroupTreeNode. I have a list of these objects in a class that inherits BusinessListBase