Moving Old App to C#

[Ron Mexico]

Hi,
Currently have an app that maintain that is written in VB6 and uses an
access db (backend db only used as a data store not writing to the db).
This app is a client app not server multi-teir app. It multi-form app that
takes in a lot of user input and gives out high end calculations
(engineering app). This app is starting to grow beyond the design and
becoming very hard to maintian. I was considering moving it to C#. All of
our new development is in C# - mostly server apps. I understand the
benefits going to .Net (no dll hell, OO, framework...) however it seems that
benefits are for web apps (web services), server apps.... A rewrite would
be a huge project and was wondering what others think.

[Bob Powell [MVP]]

While the migration from VB6 to VB.NET might not be as simple as you would
wish, I think that many of the subroutines would be eminently translatable.
Why go to C# if the application is patently a VB one? Far be it from me to
advocate for a VB solution but sometimes you have to go with what seems
right!

You say that all your new development is in C#. Is this passed down from on
high or a real engineering descision?

--
Bob Powell [MVP]
Visual C#, System.Drawing

Ramuseco Limited .NET consulting
http://www.ramuseco.com

Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm

Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm

All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.

"Ron Mexico" <ro**@mvick.com> wrote in message
news:uj*************@TK2MSFTNGP11.phx.gbl...

Hi,
Currently have an app that maintain that is written in VB6 and uses an
access db (backend db only used as a data store not writing to the db).
This app is a client app not server multi-teir app. It multi-form app
that takes in a lot of user input and gives out high end calculations
(engineering app). This app is starting to grow beyond the design and
becoming very hard to maintian. I was considering moving it to C#. All
of our new development is in C# - mostly server apps. I understand the
benefits going to .Net (no dll hell, OO, framework...) however it seems
that benefits are for web apps (web services), server apps.... A rewrite
would be a huge project and was wondering what others think.

[Ron Mexico]

We made the move to C# from VB/C++ when .Net was released because at first
it was thought that C# was the language choice of Microsoft (being
superior). Also, most of us are used to and like C++ syntax. The only
reason this app is in VB versus C++ was time because it is a highly UI
intensive app. The main reason I was looking to doing a rewrite is because
the App is gone beyond the main design (which VB could handle) and I could
redesign a more elegant/more maintainable solution using C# (OO, ADO.Net,
easier installation (no dll hell)...). Who knows when Microsoft will stop
supporting VB6 on new OS's (it could be a long time or maybe never) so
eventually I will have to rewrite this app. Right now it is about 100,000
lines of code but in the future I could see it double or maybe tripling.
It's not like I am just doing maintanence; I am actually enhancing the app
and adding more functionality.

Thanks
"Bob Powell [MVP]" <bob@_spamkiller_bobpowell.net> wrote in message
news:ug*************@TK2MSFTNGP11.phx.gbl...

While the migration from VB6 to VB.NET might not be as simple as you would
wish, I think that many of the subroutines would be eminently
translatable. Why go to C# if the application is patently a VB one? Far be
it from me to advocate for a VB solution but sometimes you have to go with
what seems right!

You say that all your new development is in C#. Is this passed down from
on high or a real engineering descision?

--
Bob Powell [MVP]
Visual C#, System.Drawing

Ramuseco Limited .NET consulting
http://www.ramuseco.com

Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm

Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm

All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.

"Ron Mexico" <ro**@mvick.com> wrote in message
news:uj*************@TK2MSFTNGP11.phx.gbl...

Hi,
Currently have an app that maintain that is written in VB6 and uses an
access db (backend db only used as a data store not writing to the db).
This app is a client app not server multi-teir app. It multi-form app
that takes in a lot of user input and gives out high end calculations
(engineering app). This app is starting to grow beyond the design and
becoming very hard to maintian. I was considering moving it to C#. All
of our new development is in C# - mostly server apps. I understand the
benefits going to .Net (no dll hell, OO, framework...) however it seems
that benefits are for web apps (web services), server apps.... A rewrite
would be a huge project and was wondering what others think.

[Peter N Roth]

gee, Ron, that sounds enormous. I count my effort
successful when i can throw code away!

Seriously, if you havent had the chance yet, check
out Refactoring by Fowler.
--
Grace + Peace,
Peter N Roth
Engineering Objects International
http://engineeringobjects.com
Home of Matrix.NET
"Ron Mexico" <ro**@mvick.com> wrote in message
news:uo**************@TK2MSFTNGP15.phx.gbl...

We made the move to C# from VB/C++ when .Net was released because at first
it was thought that C# was the language choice of Microsoft (being
superior). Also, most of us are used to and like C++ syntax. The only
reason this app is in VB versus C++ was time because it is a highly UI
intensive app. The main reason I was looking to doing a rewrite is because
the App is gone beyond the main design (which VB could handle) and I could
redesign a more elegant/more maintainable solution using C# (OO, ADO.Net,
easier installation (no dll hell)...). Who knows when Microsoft will stop
supporting VB6 on new OS's (it could be a long time or maybe never) so
eventually I will have to rewrite this app. Right now it is about 100,000
lines of code but in the future I could see it double or maybe tripling.
It's not like I am just doing maintanence; I am actually enhancing the app
and adding more functionality.

Thanks
"Bob Powell [MVP]" <bob@_spamkiller_bobpowell.net> wrote in message
news:ug*************@TK2MSFTNGP11.phx.gbl...

While the migration from VB6 to VB.NET might not be as simple as you
would wish, I think that many of the subroutines would be eminently
translatable. Why go to C# if the application is patently a VB one? Far
be it from me to advocate for a VB solution but sometimes you have to go
with what seems right!

You say that all your new development is in C#. Is this passed down from
on high or a real engineering descision?

--
Bob Powell [MVP]
Visual C#, System.Drawing

Ramuseco Limited .NET consulting
http://www.ramuseco.com

Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm

Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm

All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.

"Ron Mexico" <ro**@mvick.com> wrote in message
news:uj*************@TK2MSFTNGP11.phx.gbl...

Hi,
Currently have an app that maintain that is written in VB6 and uses an
access db (backend db only used as a data store not writing to the db).
This app is a client app not server multi-teir app. It multi-form app
that takes in a lot of user input and gives out high end calculations
(engineering app). This app is starting to grow beyond the design and
becoming very hard to maintian. I was considering moving it to C#. All
of our new development is in C# - mostly server apps. I understand the
benefits going to .Net (no dll hell, OO, framework...) however it seems
that benefits are for web apps (web services), server apps.... A
rewrite would be a huge project and was wondering what others think.

[Ron Mexico]

Peter,

I have read the Refactoring book and I have done alot of changes since
reading. I think moving the app to .Net could help eliminate some of the
code. I am 90% on moving the app to .Net I was wondering what other people
are doing with older apps.

Thanks

"Peter N Roth" <re***********@mycompany.com> wrote in message
news:ej**************@TK2MSFTNGP09.phx.gbl...

gee, Ron, that sounds enormous. I count my effort
successful when i can throw code away!

Seriously, if you havent had the chance yet, check
out Refactoring by Fowler.
--
Grace + Peace,
Peter N Roth
Engineering Objects International
http://engineeringobjects.com
Home of Matrix.NET
"Ron Mexico" <ro**@mvick.com> wrote in message
news:uo**************@TK2MSFTNGP15.phx.gbl...

We made the move to C# from VB/C++ when .Net was released because at
first it was thought that C# was the language choice of Microsoft (being
superior). Also, most of us are used to and like C++ syntax. The only
reason this app is in VB versus C++ was time because it is a highly UI
intensive app. The main reason I was looking to doing a rewrite is
because the App is gone beyond the main design (which VB could handle)
and I could redesign a more elegant/more maintainable solution using C#
(OO, ADO.Net, easier installation (no dll hell)...). Who knows when
Microsoft will stop supporting VB6 on new OS's (it could be a long time
or maybe never) so eventually I will have to rewrite this app. Right now
it is about 100,000 lines of code but in the future I could see it double
or maybe tripling. It's not like I am just doing maintanence; I am
actually enhancing the app and adding more functionality.

Thanks
"Bob Powell [MVP]" <bob@_spamkiller_bobpowell.net> wrote in message
news:ug*************@TK2MSFTNGP11.phx.gbl...

While the migration from VB6 to VB.NET might not be as simple as you
would wish, I think that many of the subroutines would be eminently
translatable. Why go to C# if the application is patently a VB one? Far
be it from me to advocate for a VB solution but sometimes you have to go
with what seems right!

You say that all your new development is in C#. Is this passed down from
on high or a real engineering descision?

--
Bob Powell [MVP]
Visual C#, System.Drawing

Ramuseco Limited .NET consulting
http://www.ramuseco.com

Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm

Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm

All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.

"Ron Mexico" <ro**@mvick.com> wrote in message
news:uj*************@TK2MSFTNGP11.phx.gbl...
Hi,
Currently have an app that maintain that is written in VB6 and uses an
access db (backend db only used as a data store not writing to the db).
This app is a client app not server multi-teir app. It multi-form app
that takes in a lot of user input and gives out high end calculations
(engineering app). This app is starting to grow beyond the design and
becoming very hard to maintian. I was considering moving it to C#.
All of our new development is in C# - mostly server apps. I understand
the benefits going to .Net (no dll hell, OO, framework...) however it
seems that benefits are for web apps (web services), server apps.... A
rewrite would be a huge project and was wondering what others think.