asked on Advice
Hi Just wondered if anyone had an opinion on how I should created a new Point Of Sale system.
I currently have one in access with sql back end. I am thinking of windows forms(c#) with Sql. I have thought about wpf but have found it difficult to work with, probably just because I don't know what I am doing.
I would hope this program would still be running in 10 years and not obsolete.
Will wpf replace windows forms?
I would probably use datasets and datareaders, is this old?
Should I use LINQ or entity framework?(not really familiar with either)
Finally would a stored procedure run faster than a LINQ query selecting 100,000 records for example.
I know this is a pretty open question but just looking for a few pointers or insights.
Thanks
Eamon
I currently have one in access with sql back end. I am thinking of windows forms(c#) with Sql. I have thought about wpf but have found it difficult to work with, probably just because I don't know what I am doing.
I would hope this program would still be running in 10 years and not obsolete.
Will wpf replace windows forms?
I would probably use datasets and datareaders, is this old?
Should I use LINQ or entity framework?(not really familiar with either)
Finally would a stored procedure run faster than a LINQ query selecting 100,000 records for example.
I know this is a pretty open question but just looking for a few pointers or insights.
Thanks
Eamon
C#Microsoft SQL ServerMicrosoft Development
Last Comment
Éric Moreau
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
ok I think I will stick with the stored procedures. Any last comments on windows forms v wpf before I close this.
Thanks
Thanks
Forms vs wpf
oranges vs lemons
coffee vs tea.
In the end it is what you are happiest working with
everything else is just a religious argument.
oranges vs lemons
coffee vs tea.
In the end it is what you are happiest working with
everything else is just a religious argument.
>>Any last comments on windows forms v wpf before I close this
Both technologies are not dead but they are not what Microsoft is pushing hard. Windows forms can't die because there are just simply too many apps. WPF is so closed to SilverLight that I wouldn't start a new project in WPF (but would go to SilverLight instead of WPF). It is possible to create modern UI using Windows Forms (have you seen Telerik latest Metro UI - http://www.telerik.com/products/winforms.aspx)?
Both technologies are not dead but they are not what Microsoft is pushing hard. Windows forms can't die because there are just simply too many apps. WPF is so closed to SilverLight that I wouldn't start a new project in WPF (but would go to SilverLight instead of WPF). It is possible to create modern UI using Windows Forms (have you seen Telerik latest Metro UI - http://www.telerik.com/products/winforms.aspx)?
Lowfatspread if I had written it in .net 2003 I would constantly upgarded it as each visual studio came out so now I would be using 2010 so hardly ancient.
What I am really wondering is if windows form will still be around or if wpf is the direction everything is heading.
You both seem in favour with stored procedures which is good for me anyway.