John Browne

HI Clara, Please email [email protected] to have a sales representative follow up. Pricing is determined by several factors (size and complexity of the application), so we'd need to get some details to give you a quote.

Visual Basic supports a way to call external classes with the CreateObject() function. The function takes a class name as a parameter. Here's an example: Dim ExcelSheet As Object Set ExcelSheet = CreateObject("Excel.Sheet") In this case, the parameter for the function is a string literal ("Excel.Sheet") and the VBUC will migrate the VB6 code correctly. However... Suppose you have this VB6 code: Const XL = "Excel.Sheet" [some code] CreateObject(XL) In this case the VBUC will display the error "CreateObjects statements using a variable instead of a literal string" in the output code. This is because the value of the variable "foo" can change over time. In this case, it's advisable to replace the variable in the CreateObject syntax with the actual name of the object class being called: CreateObject(Excel.Sheet)

Can you post the before and after code (VB6 and C#)?

Look in the VBUC references screen to see if that DLL was referenced by your original VB6 project. The VBUC would not create this--it's some kind of private library, not a Microsoft .NET library.

Visual Studio is telling you that you have a dependency on a DLL (AMB_Test5Support.dll) that it can't find in the location listed in your project file. Check your development environment and point VS to the correct path for that DLL and you should be ok.

Glad we could help!

Based on your log file, it looks like you might have a corrupted installation of VBUC. It happens--I had the same problem not that long ago. Good news is you can follow the steps here to fix it: https://www.mobilize.net/vbtonet/error-retrieving-the-com-class-factory-for-component-with-clsid-7b11c67c12-105a-4f42-a5c8-cb9070f2855a7d-failed-due-to-the-following-error-80040154

Even if you don't have a license for the VBUC you can still use it to analyze your VB6 application. This analysis will provide you with some information about your project(s) like number of lines of code (LOC), design lines, components, and more. Launch the VBUC and point to a folder containing a *.vbp file (valid VB6 project). Then go to the Tools menu and click Assessment: Click run, and the assessment will process all the files it finds. If you get an "unresolved references" warning, you can click the "Resolve References" button on the left and resolve those references (right click the missing reference and browse to its external location). Results will appear in a browser:

As Olman said above, not all properties, methods, or events from ActiveX components are guaranteed to be supported by newer, equivalent classes in .NET

How do you get a license for the VBUC trial? This question comes up frequently. When you sign up for a trial, our bot will automatically send you a "welcome" email with a .lic file attached. You can save that file somewhere and browse to it from the licensing screen inside the VBUC. The license will let you TEST the VBUC on a VB6 project up to 10,000 lines of code. But sometimes the email gets blocked, or sent to a spam folder, because it has an attachment. You don't actually need the email at all. You can download the license directly from inside the VBUC licensing screen. This article explains how. Your only requirement is to use the same email address you used to sign up for the trial. That's how we index the database--if you use a different email address we won't be able to generate a license. If you need larger trial license, contact us. We can arrange for that in most cases but we need to understand the reason first.

It looks like the problem might be related to the existing installation of VS2010. The installer looks for a file called VSIXInstaller.exe which is also on your VS2010 instance; but the SL Bridge doesn't support 2010 so there's a built in conflict. Suggestion is to rename C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\VSIXInstaller.exe to vsixinstaller.bak, then re-run the SL Bridge setup program. After it's completed, you can rename the VS2010 file back to .exe. Note: we're not sure this will work, but it's easier than uninstalling VS2010.

Sorry for the delay, this is a bit puzzling. We think it might be related to the version(s) of Visual Studio installed on the dev machine. Can you check and tell us please which versions of Visual Studio are installed?

Hi @wangw, you inspired me to write a blog post about this problem and how to fix it. You can read it here: https://www.mobilize.net/blog/vb6-to-.net-missing-a-reference

Hi Zimo85, Can you provide a little more information? Did you have the Silverlight Bridge previously installed? If so, did you uninstall it before running this setup using the Control Panel or did you uninstall it from inside Visual Studio?

This has cropped up before: it's a VS problem. See and also here: https://connect.microsoft.com/VisualStudio/feedback/details/2891723/microsoft-appxpackage-targets-causes-build-failures for a workaround.