DevComponents DotNetBar 14.1.0.0 With Source Code
Erinn Hickel
The DotNetBar assembly is about 2MB in size, although if you purchase the source code, you've obviously got the option of integrating functionality directly into your EXE file. Source code is entirely in C#, and at a mere 55 extra, it's well worth getting.
DevComponents supplies a huge number of sample applications, with source code in both C# and VB.NET. This is one of the best .NET user interface libraries we've seen and it has a very reasonable price. Dave Jewell
Today we are releasing DotNetBar for WPF 7.3 with shiny new DataForm control which makes it easy for you to create editable forms. DataForm control can create editable form without any input on your parts by examining properties on your object and creating appropriate editors for each editable property. Of course, you can specify which properties will be displayed and which editors will be used by either marking your properties with our custom attributes or by providing 100% XAML based definitions as well as using code only.
New release of DotNetBar for WPF 7.3 also includes our new samples explorer which is by default started after you complete the install. You can find complete source code for this app as well in My Documents\DotNetBar for WPF Samples.
So if you want to find out how to create controls or setup things from code you can easily discover how to do that by doing what you want to do from code in VS.NET designer, say adding controls to the form and changing their properties, then you go to InitializeComponent() method and look through code that is generated and which shows how to create everything you see on the form. The easiest is to start with new form and simply add the controls to it and change their properties then go to InitializeComponent method to see how its done from code.
Today we are releasing 11.5 version of DotNetBar with brand new Layout Control. LayoutControl helps you create resolution and DPI independent user interface data entry forms. Its built-in layout logic will re-flow its content to fit available bounds and size constraints. Following screen-shot shows the layout control in action with two different sizes of host form and without any code necessary on your part:
You can analyze applications using Veracode Static Analysis or Veracode Software Composition Analysis (SCA) upload and scan, if licensed. For SCA agent-based scan requirements, see Using Veracode SCA with Programming Languages.
Although Veracode can analyze .NET applications compiled with optimizations, the line numbers that report flaws may be incorrect. The optimization process restructures the application without updating the debug information that provides the line numbers. For most actionable results with correct line numbers, submit the application with optimization disabled.
For both debug and non-debug builds, Veracode can scan .NET code that you have obfuscated with Dotfuscator Community Edition. Do not use code obfuscation tools other than Dotfuscator Community Edition. Using other code obfuscation tools may prevent the static binary scan from succeeding.
To analyze the open-source risk of your compiled .NET application as part of a Veracode Static Analysis, upload your .NET_project_name.deps.json (preferred) file or project.assets.json file to Veracode. If neither file is available, Veracode SCA scans your application DLLs, but your results may be less accurate.
I believe the real power of XAF is your special way of handling the MVC pattern. Adding a property to a Business Object - no matter if doing it in code or with the Application Model Editor - all possible types of views can show the new values: Detail View, List View, Reports, Statistics, etc. This is really stunning and flabbergasts me every time I see it. You've really done a great job. To be honest I've developed something very similar in the past and used it now for a long time for my projects. But XAF is much more powerful and easier to use. Not to mention your great UI components.
b9b4d2437c