[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 260
  • Last Modified:

upgrade to newer development system on micosoft server

our applications are written in VB6, on 2003 XP R2.  our database server use SQL2005.  our data center told us that the end of life of XP R2 will be June, 2015. (less then 3 years).  suggest we start to look ways to upgrade.

what are the suggestions/options we have.  Ideally do not have to re-write the VB6 code.  (may not have the choose).  but we want stay on Micosoft platform.  

I am looking for suggestions.

thank you
0
mshox1
Asked:
mshox1
  • 4
  • 3
1 Solution
 
Kyle AbrahamsSenior .Net DeveloperCommented:
If you're not using any custom DLLs or anything like that you can actually use Visual Studios 2003 to upgrade your vb6 project.

From there you can migrate it to 2010 and be up to date with the latest and greatest.

There will be some errors but the advantage is you get into the .net Framkework.
0
 
mshox1Author Commented:
that is good news, we do not use any customer DLL.  I think we may even have an visual studios 2005 somewhere we purchased a while ago.  is visual studio 2003 is the only one can do what you suggested?  please clearify.  thansk
0
 
Kyle AbrahamsSenior .Net DeveloperCommented:
I believe 2003 is the only IDE that will upgrade from VB6.  

If you have a VM it's fairly easy to install.  MSDN might still have the installer, if not, I'm sure someone has an install file on the net.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
mshox1Author Commented:
ok.  I will give a try on 2003 IDE to an VM we have.  thank you
0
 
mshox1Author Commented:
one follow up questions.  we current use the vb6 with sp5 as IDE.  if we are trying to use the 2003 studio starting our upgrading step stone.  if should make sense to have the new enviorment on a seperated PC.   I think it make sense to start to acquire a new PC, that powerful enough to install the VM.  have the new 2008 R2 OS (with 2003 IDE installed),  as "vm1" and set up  VM2 (on the same PC) to install the current XP professional with current VB6 SP5 IDE).  we even should consider to set up VM3 as database server on the same PC.  - I believe the current PC hardware should be powerful enough to handle this kind of setup.  -

My questoin are:  1. if above configuration make sense?  2. what kind of laptop that you would suggest (dell, Hp, or Thinkpad?)  hopefully, the physical machine should be compact, ultra lights (less than 4 lb)?   any suggestions?

thanks
0
 
Kyle AbrahamsSenior .Net DeveloperCommented:
If you're going to buy a machine no need for the VM unless you were going to have the 2008 R2 on it.  I would NOT put the IDE on the server itself, but have a VM for a test deploy machine that will replicate your production environment.  You could create another VM (say windows 7 or even an XP machine with both 2003 and 2010 on it just for development upgrade purposes), or you can install that directly onto the laptop.

In terms of a specific laptop I couldn't really tell you, though I do recommend HP (and sometimes dell but they're normally overpriced) for business.  Reach out to the vendors, tell them you want an i3 or i5 chip and see what they recommend.  To put things in perspective, 2003 was released almost 10 years ago, any hardware should be sufficient to run that IDE.

For 2008 server things are slightly different, however it doesn't need to be production quality, just in the general ball park so you can kind of know how it will behave.  Note that using a vm though (especially on the same machine) keeps everything local.  You don't gain some of the nuances in terms of network delays and multiple users.
0
 
mshox1Author Commented:
thank you.  I appreciate the input.
this is what we are taking:

- we download the vs2008 express to our backup VM server (same disk image as production srv, but keep use the 2003 xp R2 as operating system).   we just use the upgrade wizard to migrate the 1 vb code that we consider as base line componets to vb.net.   resolve any issues we have on vb.net.   we are going to use this process to get us up to speed on the .net first.

thank you again.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now