CSLA .NET

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

Search

  • Re: Changing App Server Endpoint at Runtime

    JonnyBee, Thank you for the reply. I tried messing with the ApplicationContext to see if I could get the DataPortal to recognize the changes I was making to my configuration file. Nothing I tried would work. After looking into it further, the real issue seems to be how the default WCF ChannelFactory handles reading endpoint data from configuration.
    Posted to CSLA .NET discussion (Forum) by rlhiggin on Wed, Aug 29 2012
  • Changing App Server Endpoint at Runtime

    Hey folks, I am working on a "check out" concept in our application currently. For this concept I need the ability to change the app server that our client is pointing to at run time. Right now I have implemented this context switch by isolating my wcf client configuration into a separate config file that is referenced by setting the configSource
    Posted to CSLA .NET discussion (Forum) by rlhiggin on Wed, Aug 22 2012
  • Re: Performance of LoadProperty Method

    Gotcha. That's the part I was missing when I started wondering why the non-generic implementation was needed.
    Posted to CSLA .NET discussion (Forum) by rlhiggin on Mon, Apr 30 2012
  • Re: Performance of LoadProperty Method

    I set up a test to try out the SafeDataReader implementation to see what the performance benefit of the generic version of LoadProperty. The 5633 records were returned in 0.76 seconds. The problem with this however is that it does not handle nullable properties very well. For example, we have several properties on this object that are defined as PropertyInfo<int
    Posted to CSLA .NET discussion (Forum) by rlhiggin on Mon, Apr 30 2012
  • Re: Performance of LoadProperty Method

    The PropertyInfo is definitely declared properly. It's the second parameter that is causing it to use the non-generic overload. The signature for the generic is: LoadProperty<P>(PropertyInfo<P> propertyInfo, P newValue) The signature for the non-generic version is: LoadProperty(IPropertyInfo propertyInfo, object newValue) I'll use
    Posted to CSLA .NET discussion (Forum) by rlhiggin on Mon, Apr 30 2012
  • Re: Performance of LoadProperty Method

    [quote user="asp2go"] What is the use case for which you require such a huge list to be returned? These scenarios should typically be handled by server side/ database paging and filtering which is seamless to the user when done properly. [/quote] I'm not entirely sure yet whether or not we will actually need to return this many records
    Posted to CSLA .NET discussion (Forum) by rlhiggin on Mon, Apr 30 2012
  • Re: Performance of LoadProperty Method

    JohnnyBee, I'd prefer to not post the code because this is an army project and I don't know exactly what the policy would be for posting source code. That being said, our PropertyInfo fields are defined exactly the same way as what you have in your example. My data access is being done via SQL data reader. Using your example, the code to load
    Posted to CSLA .NET discussion (Forum) by rlhiggin on Mon, Apr 30 2012
  • Performance of LoadProperty Method

    Hi folks, My team is working on a WPF application using CSLA 4.2.1 for our business layer implementation. We have one area within our application that currently displays a list of 5633 info objects. This list is taking approximately 3.0 seconds to load. So, I decided to investigate in order to determine what the bottleneck is. I discovered that the
    Posted to CSLA .NET discussion (Forum) by rlhiggin on Fri, Apr 27 2012
Page 1 of 1 (8 items) | More Search Options

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