Windows or WPF?
-
I've taken on a small project, to write a client/purchase/sales register for an antiques/second-hand shop. The client wants a software suite that will answer some unique questions to his business, and having looked round at off the shelf software he decided that he needs a package written just for him. It will only be for his use, and not for eCommerce. That might come later, but it's not definite. I've written lots of packages like this, in VB6 and for the past five years in C#, but I'm beginning to think that I might step out of my safety zone and try to write it in WPF. However, I have no experience whatsoever in this, and would welcome any advice you can give me. Thanks in advance, George
-
I've taken on a small project, to write a client/purchase/sales register for an antiques/second-hand shop. The client wants a software suite that will answer some unique questions to his business, and having looked round at off the shelf software he decided that he needs a package written just for him. It will only be for his use, and not for eCommerce. That might come later, but it's not definite. I've written lots of packages like this, in VB6 and for the past five years in C#, but I'm beginning to think that I might step out of my safety zone and try to write it in WPF. However, I have no experience whatsoever in this, and would welcome any advice you can give me. Thanks in advance, George
Refer: wpf-or-windows-forms-opinions[^]
-
I've taken on a small project, to write a client/purchase/sales register for an antiques/second-hand shop. The client wants a software suite that will answer some unique questions to his business, and having looked round at off the shelf software he decided that he needs a package written just for him. It will only be for his use, and not for eCommerce. That might come later, but it's not definite. I've written lots of packages like this, in VB6 and for the past five years in C#, but I'm beginning to think that I might step out of my safety zone and try to write it in WPF. However, I have no experience whatsoever in this, and would welcome any advice you can give me. Thanks in advance, George
Do you think a (I hope) paying customer should pay for you to sit there and learn something new, especially something with such a steep learning curve? I hope you're not charging him for this.
A guide to posting questions on CodeProject
How to debug small programs
Dave Kreskowiak -
Do you think a (I hope) paying customer should pay for you to sit there and learn something new, especially something with such a steep learning curve? I hope you're not charging him for this.
A guide to posting questions on CodeProject
How to debug small programs
Dave KreskowiakAs an honest trader, I'll only bill for what he gets. There's a lot of cowboys out there that don't, And this is in the wop-wops where clients rapidly become friends.
-
Refer: wpf-or-windows-forms-opinions[^]
Sorry, should have checked first. Mea Culpa.
-
I've taken on a small project, to write a client/purchase/sales register for an antiques/second-hand shop. The client wants a software suite that will answer some unique questions to his business, and having looked round at off the shelf software he decided that he needs a package written just for him. It will only be for his use, and not for eCommerce. That might come later, but it's not definite. I've written lots of packages like this, in VB6 and for the past five years in C#, but I'm beginning to think that I might step out of my safety zone and try to write it in WPF. However, I have no experience whatsoever in this, and would welcome any advice you can give me. Thanks in advance, George
-
Windows Form based development is different from doing WPF. I would recommend doing what you are comfortable with. After all, someone else is paying for a software product he needs and not for you learning new things.
I've taken that into account, I think I'm going to do the project in both, Window Forms and WPF. That way, I'll only bill for the forms development (I can write it in my sleep anyway, there's nothing earth shattering about it).
-
I've taken that into account, I think I'm going to do the project in both, Window Forms and WPF. That way, I'll only bill for the forms development (I can write it in my sleep anyway, there's nothing earth shattering about it).
-
I've taken on a small project, to write a client/purchase/sales register for an antiques/second-hand shop. The client wants a software suite that will answer some unique questions to his business, and having looked round at off the shelf software he decided that he needs a package written just for him. It will only be for his use, and not for eCommerce. That might come later, but it's not definite. I've written lots of packages like this, in VB6 and for the past five years in C#, but I'm beginning to think that I might step out of my safety zone and try to write it in WPF. However, I have no experience whatsoever in this, and would welcome any advice you can give me. Thanks in advance, George
depends on how large and complicated it is. I would recommend a good book to start from. If you have done Asp.Net you'll feel comfortable reasonably quick (it is more similar to designing web pages than in designing forms). However if the project is large or could become large, it is probably better to keep with what you know.
V.
(MQOTD rules and previous solutions)OriginalGriff wrote:
V is absolutely right
-
Thanks for the reference, I'll have a good look at it this morning.
-
depends on how large and complicated it is. I would recommend a good book to start from. If you have done Asp.Net you'll feel comfortable reasonably quick (it is more similar to designing web pages than in designing forms). However if the project is large or could become large, it is probably better to keep with what you know.
V.
(MQOTD rules and previous solutions)OriginalGriff wrote:
V is absolutely right
It's not a big project by any stretch, but it's one of those that has the capability of growing. I've written the same kind of thing lots of times before. There's just one (new) bit I'm unsure of, and that's a legal requirement to identify sellers (The New Zealand second hand dealers act is quite rigid on that), but I'm sure I'll find a way to do it.