EDN Admin
Well-known member
I am converting an older software package written in VB 6 to VS 2010. Not to incredibly painful but planning for the future as we have had lets say a few issues with VB 6 on our current layout of multiple OS and this is my first real project lead.
We are a smaller job shop and we move on a rotation of new PCs/OSs come in to replace broken or exhausted older PCs in the front office and move the older PCs out to the shop floor. We have an array of different OSs ranging from Windows 98 and Windows
7 (32 bit and 64 bit OS). By the time I am done with the conversion we should be sitting comfortable with a range of PCs from XP and up. When creating the executable for my project is this something that can be handled ahead of time, creating
multiple executables for specified OS, or an all in one package executable?
I was looking to see what people had as suggestions at handling this. We havent even bought VS yet and are looking at the VS 2010 Premium package, do I need Ultimate?
View the full article
We are a smaller job shop and we move on a rotation of new PCs/OSs come in to replace broken or exhausted older PCs in the front office and move the older PCs out to the shop floor. We have an array of different OSs ranging from Windows 98 and Windows
7 (32 bit and 64 bit OS). By the time I am done with the conversion we should be sitting comfortable with a range of PCs from XP and up. When creating the executable for my project is this something that can be handled ahead of time, creating
multiple executables for specified OS, or an all in one package executable?
I was looking to see what people had as suggestions at handling this. We havent even bought VS yet and are looking at the VS 2010 Premium package, do I need Ultimate?
View the full article