vb6-migration

I am in the process of migrating a legacy VB6 app to .Net, however since it is a high-profile business critical application, it is being done piece by piece. In the interest of improving performance, there is one method which gets hit a lot,thousands of times during the application life, and I was wanting to rewrite it in .Net (C#) to see if the runtime can be improved. The method in question manipulates ADODB Recordsets. Is there any performance issues I should be aware of or take into consideration since these recordsets will be passed to and from VB6 via COM interop? I haven't done anything

I need to convert a VB6(which I'm not fammiliar with) project to C# 4.0 one. The project contains some regexes for string validation. I need to know if the regexes behave the same in both cases, so if i just copy the regex string from the VB6 project, to the C# project, will they work the same? I have a basic knowledge of regexes and I can just about read what one does, but for flavors and such, that's a bit over my head at the moment. For example, are these 2 lines equivalent? VB6: isStringValid = (str Like "*[!0-9A-Z]*") C#: isStringValid = Regex.IsMatch(str, "*[!0-9A-Z]*"); Thanks! The old

I'm migrating some VB6 code to VB.net, the code contains a structure that contains 1d arrays, 2d arrays, and few other variables. The general outline of the Vb.net structure is as under Public Structure Test Dim a As Single Dim b As Single Dim c As Single <VBFixedArray(2)> Dim arr1() As Single <VBFixedArray(2, 2)> Dim mdarr1(,) As Single <VBFixedArray(4)> Dim arr2() As Byte <VBFixedArray(4)> Dim arr3() As Short <VBFixedArray(3, 2)> Dim mdarr2(,) As Integer Dim d As Integer Dim e As Decimal End Structure The call to the dll is declared as under Public Declare Sub getState Lib "val.dll" (ByRef

I have created a manifest file for a VB6 application that is running on Windows 7 (not for any visual style changes, just to make sure it accesses the common registry and not a virtualised one) The exe name is Capadm40.exe, the manifest is named Capadm40.exe.manifest and contains the following: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> <assemblyIdentity version="1.0.0.0" processorArchitecture="X86" name="CompanyName.Capadm40" type="win32"/> <description>Administers the System</description> <!-- Identify the

I have some VB6 code that needs to be migrated to VB.NET, and I wanted to inquire about this line of code, and see if there is a way to implement it in .NET Dim strChar1 As String * 1 Intellisense keeps telling me that an end of statement is expected. That's known as a "fixed-length" string. There isn't an exact equivalent in VB.NET. Edit : Well, OK, there's VBFixedStringAttribute , but I'm pretty sure that exists solely so that automated migration tools can more easily convert VB6 code to VB.NET for you, and it's not really the ".NET way" to do things. Also see the warnings in the article for

I am converting some VB6 code to VB.Net. Since my VB6 installation appears to be damaged beyond repair I am using Notepad to read the original source code and can see at near the top of the file:- Attribute VB_Name = "clsBulge" Attribute VB_GlobalNameSpace = False Attribute VB_Creatable = True Attribute VB_PredeclaredId = False Attribute VB_Exposed = False Attribute VB_Description = "Some text here" Attribute VB_Ext_KEY = "SavedWithClassBuilder" ,"Yes" Attribute VB_Ext_KEY = "Member0" ,"collBulges" Attribute VB_Ext_KEY = "Top_Level" ,"Yes" and down in among the works:- Public Property Let

I am trying to convert a large (200K lines) VB6 project into C#. I only want to convert the form design because I want to rewrite all the actual code in C#. I want to use the free Artinsoft converter but this only allows projects of 10K lines. I am thinking I could break the VB6 project into 20 separate projects and then generate the C#.NET forms by using Artinsoft, then bringing the converted forms back into one C# project. Is this feasible? EDIT: Will this work? What are the potential problems? I will try it in following order 1) Write automated test cases at least for major business