WPF and SQL/Relational Dababase Applications - Am I wrong

Dennis Triplett

15y4k

Just a quick question and observation... I am going to be developing intensive, SQL or MySql, Relational Database applications. After some searching of the net, I see that even VS 2010 pro isn't much more capable than VS 2008 in designing relational Database WPF applications. Am I correct or do I have it wrong? Please say I'm wrong. :(

It looks like I might have to co-design Form, WPF and .Net Link to create my applications. Again, please tell me I'm wrong.

I am hoping that I can develop exclusively with WPF and create SQL intensive DB applications.

Any feedback or directions where to find this answer is greatly appreciated.

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

Dennis Triplett15y ago
Well, this is *really* good to hear Mahesh... Because I haven't created my app yet, but read that WPF wasn't very relational DB friendly... which is why I asked here.

Again, I'm just starting WPF, and as you can see, have a lot to learn... Which is why I know I'm at the right place with C-SharpCorner. I hope you don't mind my beginner questions.

Didn't mean to light your fuse though. ;o) ... but am sure glad to hear you say "Wrong and Wrong!!"

I should add that I will be upgrading from VS Pro 2008 to VS Pro 2010 in March and Expression Blend 4 Ultimate in April. I just downloaded VS Pro 2010 and Expression Blend 4 Ultimate Trial versions so I can get familiar with them.

Thanks Mahesh,
Mahesh Chand15y ago
Wrong and Wrong.

VS 2010 is much improved UI than VS 2008. Also, WPF and other designers have better support and there are several new improved controls in the Toolbox.

You can design intensive SQL DB applications using WPF.

For database connectivity, you can use ADO, ADO.NET Entity Framework, Prism kind of frameworks or LINQ.

What do you mean by co-design your application? Have you already created your application? If you have an application in VS 2008, you probably can convert it to VS 2010 by opening it in VS 2010 and follow the conversion steps.