I am currently trying to decide how to tackle a very large project at
work. I am in charge of a large program that while it currently works, I
don't feel that it handles the user’s needs well enough. It is a large
single form VB.Net project that is written very functionally. It doesn't
have any real OO structure at all. I have worked with it for two years,
and I have finally had it. I decided that I cannot band aid this program anymore
and it is time for a rewrite. Now here is the question. I am looking
at .Net 3.5 and WPF, Is it worth waiting for VS 2008 before I rewrite the
program. Also is it worth staying with VB? How should I handle the
CRUD aspects of my program? I have to use the existing database because
it is used for other programs read only of course(not my idea
). So what to
do? Well let me tell you what I figured was my best solution:
Jay's Solution to Rewriting a large program:
1. Users: As I said I don't think the current
program handles the users as well as it should. So I am going to meet
with the main users next week to talk about what is good/bad about the existing
program, and discuss what the current program doesn’t' do that it should.
Of course documentation at this point is Key!
2. When to start: Well there is no time like the
present. Right now I am in the middle of a major cycle, so my time is
limited, but I think this project is important enough to add to the
stack. I do think that WPF is worth using because of the style it adds to
existing programs, and I am hopeful that it will upgrade well to 3.5. I
do have issues installing .Net 3.0 onto client machines because of all of the
problems I have heard from my friends who do IT support for other companies
that use 3.0.
Also as long as I use good OOP upgrades from this point
shouldn't be that big of a deal. I can just upgrade my UI, or my Business
logic depending on what 3.5 offers.
3. VB or not to VB: Other people in my organization
have talked about making the move from VB to C#. I learned .Net on C#, so
I am all for it. I think VB is a second class citizen in the .Net
world. All of the examples on the web are in C#. C# gets all of the
cool features well before VB. Look at generics. I think C# is the answer,
and I can write my business logic in C# for now, and if we decide to stay in
VB, then I can change as necessary. It is better to ask forgiveness than
permission.
4. DAL: I hate writing
CRUD. Let me say that again. I hate writing Crud. I have
found Object binding to be very useful for the UI. I am going to play
with something like subsonic or active record to see if I can speed up my CRUD
development. Otherwise code generation using Code Rush will have to be
used to keep my sanity.
So there you have it. I am going to take the leap and start a few new
projects. I think the time has come to take the leap. Now it is
time to design!!
Be the first to rate this post
- Currently 0/5 Stars.
- 1
- 2
- 3
- 4
- 5