Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
What choice is the best one, coding or drop and click to generate xaml code?
If you are gonna work with visualization before doing coding or maybe doing both, should the process be taken in VS 2010 or Blend?
Is there any similiar code of WPF's C# WPF in other context for instance in Biztalk, sharepoint (except Winform) etc?
I heard that Microsoft Blend should be used for creating prototype only, is that true? Is Blend strong enough to work with user interface?
WPF makes it simple to separate the look&feel of the application and the logic behind.
Blend is used to create styles, and may be used to create GUI prototypes. All this work however can be done in VS too. It's only a matter of convenience.
If you're using Visual Studio you can install Xaml power toys add-in which is able to do many different things for you (eg. generating DataGrid columns of a business form for an entity class)
I heard that Microsoft Blend should be used for creating prototype only, is that true?
Blend is all about what you see. Vs is about the code.
If you are gonna work with visualization before doing coding or maybe doing both, should the process be taken in VS 2010 or Blend?
Definitely blend.
What choice is the best one, coding or drop and click to generate xaml code?
Doesn't matter. You do what's faster for you. I prefer typing, but someone else might prefer clicking.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I am new to GUI development and Embedded programming using DSP Processors.
I would like to build a GUI of 4 channel oscilloscope using Visual C# and Windows Forms. The signals will be communicated from DSP processor using serial port RS232.
What kind of Windows Forms controls help in building such a GUI? and how to start with the work?
If there any other useful tools to be used along with Visual studio C#?
Any useful links explaining the basics of development may be helpful.
What kind of Windows forms controls help in building such a GUI?
There is a nice tool un Windows Forms called Chart. You can draw graphs of different kind with it.
Here is a Tutorial
Here is a Video that shows how to use it.
How to start with the work?
You should start and play with this control.
Learn how to add values.
Learn how to remove values.
Learn how to bind values.
Learn how to handle the axes and the ranges to be displayed.
If there any other useful tools to be used along with Visual studio C#?Any useful links explaining the basics of development may be helpful.
here you find all different chart types that can be displayed.
and here how to use them.
This answer is partly copied from a previous one of mine.
I would suggest to search also for "online/real time display of data with chart control" or "moving chart".
This link might be usefull. It asks for almost the same as you.
Here you can find some samples
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
In Xamarin.Forms there's 2 ways to build an app's layout: in C#, or using a mix of XAML and C#. Is there any definite benefit of one over the other?
Xamarin should compile either into the respective platform apps (for droid, iOS, usw) the same, so the only differences I can see are that XAML splits the design and the code into separate files (.xaml and .xaml.cs), while the C#-only way avoids visual studio code complaining about the compiletime-generated functions in the .xaml.cs files. Is there anything I missed? A good reason to become fluent in reading the XAML markup when the C#-code is already intuitive for me?
XAML provides a more succinct and elegant definition of the user
interface, and has a visual structure that better mimics the tree
organisation of the visual elements on the page. XAML is also
generally easier to maintain and modify than equivalent code.
A declarative UI(XAML) is a better approach than doing the UI by code,
for the following reasons:
it's coincise, it's impersonal
except few things, XAML looks the same for everyone. you can't say the same thing about code-behind C# coding
it's more maintainable
much more easier to read and modify than code
it helps with a clear separation of concerns, between the UI and logic
tooling friendly; unfortunately Xamarin Forms today still doesn't have a designer, but this is supposed to change
I am NOT saying XAML is perfect. C# code is also good.
Read some similar discussions :
https://adventuresinxamarinforms.com/2015/03/17/xaml-v-code/
https://forums.xamarin.com/discussion/44117/xaml-vs-programmatically
https://forums.xamarin.com/discussion/58831/building-interfaces-xaml-vs-c-code
https://forums.xamarin.com/discussion/24682/ui-written-by-xaml-or-pure-code
Xamarin UI: Programmatically VS XAML
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I am just about to embark on a learning path in WPF. I want to make sure I'm starting as I mean to go on, by learning the correct skills first.
I have found references to WPF being used with both C# and XAML. I was wondering, in a work-environment, which do you use to develop WPF applications?
XAML is a markup language. When you write XAML for a C# application, it is simply instantiating C# objects. So, you are really writing C# either way.
XAML is essentially a declarative way to write code. It is extremely common for the User Interface (often called the View) of an application.
In my opinion, a WPF application's View should almost always be in XAML. And anything that is not UI (e.g. the business logic, or the Model), should not be written in XAML. This is standard for the MVVM Pattern, which is extremely popular for WPF development.
The short answer is that you need both XAML and C# of another programming language like VB.NET to create a WPF application.
At the very beginning of your learning process you can get away with only learning XAML. Which is actually a good idea anyway. Learn about using dependency properties, attached properties, layouting without writing a single line of code at first.
Next you can write some event handlers, but I wouldn't spent too much time on write too complex code attached directly to the XAML windows as the MVVM makes your life a lot easier.
For MVVM I recommend using a framework, for instance MVVM light from Laurent Bugnon, he also wrote some excellent books, silverlight though, which describe MVVM.
https://mvvmlight.codeplex.com/
As I side note I should add that it is possible to create your GUI completely using code and without XAML. But I would argue that this is an exceptional case. The idea of WPF is really to seperate the GUI, using the declaritive XAML, from the rest of the application that is coded. As a beginner I wouldn't embark on the path of coding your GUI without XAML.
Another side note is that XAML is also used to declaratively create workflows using WF. So XAML is not used for GUI's alone.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
I want to make an applications that works like Word, Excel, Power Point etc... I mean if you maximize or change the window size to something different the program will always adjust the inside elements in a very nice way.
I'm creating a new "WindowsFormsApplication" in Visual Studio 2012 with C#
Thanx !!
Check out http://avalondock.codeplex.com/, it provides a Visual Studio style interface out of the box, and is very extensible.
Last time I checked it didn't support MVVM so well, but that might not be such a problem.
Dynamic resizing in WinForms is very easy, and most (if not all) of the behavior you want can likely be achieved simply by choosing the right controls and property settings.
To get started in the right direction, read up on the following topics:
Control.Anchor Property
Control.Dock Property
TableLayoutPanel Class
FlowLayoutPanel Class
It is easy enough to create a quick test app and drop some controls on it to see how they behave. No coding required.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I am starting to learn c# and wanted to create an actual app which one of the two would you start with?
Personally, I would learn WPF. We use a lot of Winforms, but we're in the process of migrating to WPF. I think that's a more future proof set of skills. WPF Virtual Labs are a good place to start.
My rule of thumb is to choose the most recent technology that doesn't require your users to go through extra effort. If you have to support Windows XP, then WinForms is the way to go as it doesn't require XP users to install .NET updates. If you don't have to worry about XP, then WPF is probably the ready to go.
I recommend WPF - it is now very mature and well supported. Of course, winforms is still supported and some new development is being done for it. However, WPF is significantly more sophisticated and powerful. Almost as importantly, the tool support for it is MUCH better than for WPF.
Here are some links for you.
A Guided Tour of Windows Presentation Foundation
Windows Client .NET
WPF vs Windows Forms
I would say learn both to have a stronger foundation of knowledge and be able to work with legacy code, but put more effort into WPF because it will eventually replace WinForms.
The basics of either are much the same -- WPF offers a lot more features by way of declarative UI definition and skinning/theming, and a slightly different set of layout techniques. While you're at the "Hello world!" stages, it makes little difference -- certainly less than using either GTK# or the Swing implementation in VJSSupUILib would.