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 want to know which one is the best natural choice while working with SQL and Entity framework, c# Winform or the WPF? Assume that skilled resources available for both the technologies (Winforms and WPF).
Entity Framework doesn't care which UI technology you use on top of it.
There's no natural choice - use whatever you're comfortable with and whichever works for your needs
After working with both, I strongly recommend WPF, since it gives you a far better code/UI separation. Using MVVM makes the code more readable and easier to maintain (and read).
SQL and EF don't care how the layers above are implemented, it's your choice alone.
EF not dependand any one like if you used winfrm or WPF. but there is a difference between winform and WPF.
if you want to know then you can use the mentioned link Click here
If you want better Presentation of your application then I would recommand you to go with WPF.
Related
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 3 years ago.
Improve this question
I am beginner to .net core. And I am working on an enterprise application where there are multiple classes interfaces for multiple project inside a one solution. i know Entity Framework won't be a good idea if we are facing huge number of wrappers. But indeed its giving me efficiency of coding. On the other side of it Entity SQL has its own benefits.
But still want to really understand the best practice and which one to implement when it comes to Enterprise application knowing it will have number of classes, Data filtration, Generic Types, Flexibility, performance vise when querying DB.
Looking forward to get some really helpful understanding from experts. Thanks in advance.
TL;DR;
The "best practices" depends on the use case. Its a set of tools, not a silver bullet.
Sometimes EF works for your case, sometimes not. Sometimes you want a monolith, sometimes you dont.
Try, experiment fail and succeed.
Best practices regarding to techniques are irrelevant; implementation change all the time. So;
define functional requirements
define none functional requirements
do a PoC with some relevant loads etc.
At enterprise level consider these additional properties:
security
operational functionality
cloud / none-cloud
This is the best I can do, given your question.
Explain the case and we could give some direction; but its not a template fitted for all cases.
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
I have an existing MS access application for capturing information (normal add, edit forms with drop downs and so-forth) that I'd like to redesign into a WPF C# application using a Microsoft SQL database.
My question is, is WPF the easiest / quickest solution or are there any alternatives anyone can suggest?
I have some knowledge of WPF and a good understanding of SQL databases.
Thanks
It seems that your application is data driven so as an "easy but not so far" alternative to WPF I would suggest you to have a look at Visual Studio LightSwitch. It is especially designed to quickly create data driven screens with full CRUD hosted within Silverlight (desktop) or within HTML5 (web).
Silverlight is quite dead but it will be easy for you to jump on if you are already familiar with WPF.
Have a look here: https://www.youtube.com/watch?v=oIBJrGp-kOY
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 curious as to how one can go about creating a GUI in a similar manner to the popular Popcorn Time application? I have been learning Java, C, C++, and a tiny bit of Objective-C and I have no clue how to make my GUI look any better than that of Java's Swing framework. There seems to be a very limited level of style associated with these default layout frameworks, without getting very advanced with styling.
Is there a framework which will allow me to create better GUIs with Java without spending too much time on it? I'd like to focus on core functionality, but would also like my application to look a tad bit better than Java Swing.
Here is the type of GUI I'd like to create:
http://imgur.com/57JOB6X
Start with creating simple native GUI's, before attempting "beautiful" GUI's.
Since you told that you have an understanding in C++.
I would suggest you to learn Qt framework, which is based on C++.
I have been designing GUI's in Qt for over a year now, and occasionally i have used Qt-stylesheets
to theme certain GUI elements.
After you become familar in Qt, you can find that there is openGL, QML , javascript and other support available, to create more customized GUI's, although i have not used them.
Get started , with this simple notepad app !
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 9 years ago.
Improve this question
I'm about to develop some LOB applications using VS2012, WPF, Sql Server Express 2012, Unity, Prism.
I don't have legacy applications to care about.
Is it ok if I choose the Model First workflow for my upcoming projects, are there some important benefits in the Code First workflow that I would not be receiving?
If there's any that I could not overlook, then could I start with Model First and then switch to Code First?, it happens that I'm more confortable designing databases with the designer than by code, this is the main reason for this question.
If you're more comfortable working with databases first, I would go down that route. This question has a lot of pros/cons for each.
I've recently used code first for a project and I regret that decision. Although it is incredibly powerful, it was an unnecessary learning curve and ultimately took far too long to setup a simple schema.
If you want to learn how code first works, and time isn't an issue, then you may as well go for it. Else, what do you really have to gain from it?
Ultimately though, if you're developing it and you already have a sufficient skill set in one of these, use it.
I have created WPF applications using code first and MVVM patterns + DI (though not Prism).
It took a while to convince me to move away from the edmx models, but I've found Code First to be a much cleaner approach, with no apparent downsides.
I think you could easily move to model first from code first, though you probably wont need to. I haven't tried it - you might need automapper.
I have successfully taken existing dbs and moved over to CF though it is a bit messier.
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 9 years ago.
Improve this question
Assuming I was writing my own version of .Net :)
What would be the downside of such a setup?
Yes, I am talking about a new anti-pattern here to avoid creating endless tuples and EventArgs. I think such a setup would have made coding a lot cleaner.
No. The Tag property has history, it was important in VB6 and Winforms was meant to replace it. It needed to be added to make porting code relatively simple.
It is entirely unnecessary in .NET. It supports implementation inheritance, a feature that VB6 didn't have. So if you want to add extra properties then you just derive a class and add them. And you'll be able to give them a good name and a type so you don't have to cast every time you read the property. This works just as well with Winforms controls.