Vibrant discussion about CSLA .NET and using the framework to build great business applications.
I am maintaining an ASP.NET application that uses the CSLA framewwork. One of the things new to me that stood out was how the developer in the ASPX pages typically used the data-binding inline tag ( <%#. ..%> ) for just about everything. I've noticed some strange things where the page seems to cache old data and if I change the reference to a standard inline tag ( <%= %> ) it corrects the issue.
For example:Client Name: <%# WF.ServiceIncidentEdit.ClientName %>Changed to:Client Name: <%= WF.ServiceIncidentEdit.ClientName %>
Corrects the caching issue. I'm assuming this is some how CSLA releated, cause I can't even use data-binding line tags in a typical project without CSLA unless it's a BIND or something in a data control.
This has nothing to do with CSLA and everything to do with ASP.NET and inline script tags / rendering.
Read more here:
Jonny Bekkum, Norway
So CSLA isn't applying some type of data binding that makes the inline data binding expressions work with a simple inline function? Because it doens't work outlisde of this CSLA project.