11/12/2022 0 Comments Devexpress datecontrol v13.2![]() In my next post I’ll be taking a look at the new soft validation along with some other 13.2 improvements.Reason 2: Not supported by the old browsers. In my main development project, there are currently 110 different reports and maintaining them takes some effort. In this post, I haven’t looked at features such as views, sub-reports and custom reporting components, all of which deserve further investigation. I’m sure there are a few beta issues to iron out and a few further improvements down the line. Reports V2 is certainly the most significant improvement to the XAF reporting engine yet. #Devexpress datecontrol v13.2 code#For me at least, the benefits of having more maintainable code outweigh the inconvenience of losing the events when cloning a report. A bit unfortunate - that event would have to be re-written or copied manually from the C# source file, but in most cases, additional tailoring of reports is a one-off occasional activity. Well, the serialized event was copied correctly, but the script that we put in the C# file has not been copied. Now we can open the Report Designer and customise the report further. #Devexpress datecontrol v13.2 windows#It would be better if the new copy got renamed to Copy of Inplace Report like Windows does when copying a file). (A little suggestion to the DevExpress crew. This time it is the Copy predefined report is greyed out and the familiar Show Report Designer has become available. Also, notice that the Show Report Designer is greyed out. Unit testing of the events becomes feasible.Ĭan an end-user still make a copy and tailor the report as they could with the older versions? Yes they can! Let’s start up the WinForms client and have a look.Įach of the PredefinedReadonlyReports has a new option Copy predefined report.The source code can be merged much more easily when handling version control conflicts.The source code of the events can easily be compared with older versions.If there’s a mistake in an event, the project will not compile until it’s fixed.Here are the advantages of handling events this way. We start up the web application and run the report.Įxcellent! You can see the report has successfully run the event and is displaying the current time instead of the first name. If we look at the source for one of these, here is what it looks like: That is, the report is serialised as a string and loaded into the database during initialisation. PredefinedEditableReports contains V1 reports. Notice that there are two folders containing reports. The interesting part of the project solution is here: DevExpress have provided us with a new sample project called ReportsV2Demo. The immediate advantages of Reports V2 are: DevExpress is calling this Reports V2 and it largely supersedes my previous workarounds. This has a lot of shortcomings some of which I have addressed in previous blog posts.īut now finally it is now possible to build XAF reports directly from Visual Studio. They were objects serialized to a file and then loaded into the database during initialisation. Prior to this version, XAF reports were not source code. This part is an in-depth review of the new report writer features (still in beta). This post is the first part of an overview of the brand new version XAF 13.2 which will be released any day now. The first version of XAF I ever installed was called eXpressApp-1.0.CTP2.exe in July 2006! It has certainly come a long way since then. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |