Docking library for C# [closed] - c#

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I'm looking for a Docking library for using in the C# application. It can be designed for WPF, but I prefer WinForms applications. Of course, it should provide standart docking opportunities.
I'm going to use it in an application where user can control a huge amount of different processes which can appear and disappear dynamically during the application lifetime. Thus, the main criteria is the following: I should have opportunity to create docking windows and controls located on it dynamically and save the information about all docking windows positions in some file (content I can save using other way). After the application was relaunched it should restore all the docking windows in their states before the application close (and all of their content, but I can load it manually).
Unfortunately, I have found the only docking components library that contains all the required features - it's Telerik WinControls. But it's too slow for my purposes.
Please advise me a good docking library!

AvalonDock
It provides binding mechanisms for easy manipulation and MVVM and good serialization mechanics. It is the docking library used in SharpDevelop. Plus its free.

Actipro makes one
Actipro Docking Library
I have used the WPF version (not WinForms) of their docking library and it is pretty good. I'm not sure why you said the Telerik docking library was too slow.

Related

The latest trends in designing windows based desktop application [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I have an application written in C#, using .Net 4.0 framework. As the application is kind of an old application, so its using window forms. The application is very simple for now, it doesn't have high graphical interface like using WPF and Silverlight. I have now decided to move the application to the next level, the latest, one using current trends and great user interface. What are my options of improving this application design wise, performance wise and looks wise? Like using WPF, MS Silverlight or any other cool technology out there?
I kinda more need ideas what can I do to get to high tech application? Some examples of some cool applications would be also appreciated.
A little about the application:
Its a windows desktop application, using Access as a database used for some finance analysis.
If more information needed? Please let me know.
In short: Id say WPF is all you need technology-wise. Its really neat, i love the looks of it and its quite easy to use (especially with Expression Blend!)
On a side note:
The big issue here will be designing a good interface, not using "shinier" buttons. Currently, the UI design is getting more and more elements to it, changing to UX design. You can read about it if you google, a few links to start with:
http://msdn.microsoft.com/en-us/library/aa511258.aspx
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/industryinsights/solutions/pdfs/Forrester_Best_Prac_In_User_Exp.pdf
http://developer.android.com/design/get-started/creative-vision.html - this is about Android, but it can and should be transferred to a desktop environment
Ill use a little metaphore: Youre asking us "what kind of paint should I use for my masterpiece painting that will put Leonardo Da Vinci to shame?". Are you sure you already know what and how to do with that paint? Some artists drew masterpieces using only a single pencil, others couldnt do anything of value despite using the best tools available.

change existing Winform to wpf [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Is there any way i can change my existing winform app to WPF,i had used c#.net and SQL Server 2005, I am a first timer in WPF, please consider before answering.
thanks
No - there is no "automatic" way to switch - nor would you want to do so.
While it's possible to write WPF in a manner very similar to Windows Forms, you typically do not want to do so. It really defeats the purpose of changing. The advantages of WPF really come into play when you take advantage of Xaml and data binding to their fullest extent, which wouldn't happen with an automatic conversion.
That being said, it's always possible to start writing some of your new user interfaces in WPF, and still use them within the existing Windows Forms project (via ElementHost). This allows a transition to WPF, without having to "convert" at once.
Any application logic which is properly decoupled can be used from both Windows Forms and WPF, as is - so the only thing that has to change is the portion of your application tied to the user interface.
It depends on your project structure, WPF is all about UI. If you've a layered solution you can simply change its UI from WinForm to WPF, but There is no automatically way to do that, You have to rewrite your UI.

Financial chart component for C# [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I am in need of a component for drawing financial charts with the following features for my application:
Live plotting.
OHLC Chart, candlestick chart and previous day close chart.
Various Analysis studies.
Easy distribution with designing tools.
Thank you.
If you are developing Windows Forms or web applications, the open-source Zedgraph is a good solution. You can see examples of OHLC and candlestick charts here. There is also sufficient designer support for incorporating Zedgraph graph controls into your forms.
.NET Framework 4.0 also contains Windows Forms charting out-of-the-box, although Zedgraph is more powerful.
WPF charting is available in the WPF Toolkit on Codeplex. It is even less complete than its Windows Forms correspondent, but on WPF it should at least be a decent open-source alternative.
Highcharts or Highstock - http://www.highcharts.com/
Highcharts or Highstock are used for web development though. Is that what you're after?

Is WPF stronger than Windows Forms? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
Is WPF include all the feature of Windows Form + Additional Feature? Because I found some of features of WinForms are not available in WPF.
update me! The importance of Windows Form than WPF.
WPF is a completely different approach to user interfaces than Windows Forms.
It has a much more flexible design, which allows you to do a lot more things, often with cleaner code. This is especially true when you fully take advantage of the data binding support in WPF.
However, Windows Forms is very mature - as such, there is a huge, mature ecosystem built around it. This does include some tooling and features that don't exist in WPF.
That being said, most new development within the .NET Framework related to user interfaces is XAML based. I would strongly suggest using WPF or Silverlight over Windows Forms for any new development. I wrote a detailed series on migrating to WPF from Windows Forms which discusses many of the benefits and advantages of WPF.

Good open source Reporting tool/framework for WPF (C#) [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I am looking out for a good open source Reporting tool/framework for windows based application (WPF).
The database I am using is sql server 2005.
The typical reports format which I am interested is for e.g. Trial balance, balance sheet, etc (typical banking / finance reporting application).
There should be good support for charting as well.
If anyone has any experience with reporting for WPF application, your inputs will be highly appreciated.
Take a look at http://wpfreports.codeplex.com/
Since this may form part of the answer, I thought of putting this in the answer section.
I just found this series of article
WPF multipage reports (note: original link dead, replaced with Wayback Machine link).
Thought of putting this here as this may benefit some other learner. This article walks through creating a reporting framework for LOB Apps.
As the saying goes "A Bird in the hand is worth two in the Bush", I will have a deep look at this until something else comes up with something better :)
PdfReport is a code first reporting engine, which is built on top of the iTextSharp and EPPlus libraries. It's compatible with both .NET 3.5+ Web and Windows applications.
As open source, this doesn't exist, at least not yet.
It probably doesn't exist commerical offering either. The WPF component market is just getting started.

Categories

Resources