VBUC Documentation | Mobilize.Net
Mobilize.NetForumsBlogDocumentation Home
  • Mobilize.Net VBUC
  • Introduction
  • Install and Licenses
  • Get Started
  • Migration Guide
  • VBUC Features
  • Mappings Grammar
  • Generated Code
  • Upgrade Options
    • Data Access
    • Grids
    • Microsoft
    • Sheridan
    • Others
    • Code Conversion
    • C# Features
  • Third-party controls
  • Best Practices
  • EWIs
    • Warnings
    • Issues
    • ToDos
    • Notes
  • Issues and Troubleshooting
    • Microsoft.VisualBasic Uses
    • Safe and Unsafe Methods Layer
    • Third Party Components
    • Migration Process
    • Classic ADO Conversion to ADO.NET
    • VB6 and .NET integer division
    • VB6 On Error Statements
    • Running a .NET Core application in a machine with no Visual Studio installed
    • Databases issues
    • Unsupported assemblies on .NET Core and .NET 5
    • Icon Extraction Issues
    • HTTPS sites are not loaded in Windows XP
    • Short-Circuit Boolean Logic in C#
    • Assessment Report Issue
  • Knowledge Base
    • FAQ
      • Does the VBUC support the Sheridan VB 6.0 controls suit?
      • How effective is the Visual Basic Upgrade Companion tool at converting an application's front end?
      • What controls does the Visual Basic Upgrade Companion tool supports?
      • How does the VBUC handle VB6 Collections?
      • Can the VBUC migrate intrinsic VB6 functions and libraries?
      • Where is the source code for the support (helper) classes used by the VBUC?
      • How does the VBUC convert ADO to ADO.NET?
      • Can the Visual Basic Upgrade Companion tool be customized?
      • What are Stubs?
    • How-To
      • App.Config and Database Access
      • Avoid reflection in Hot Paths
      • Convert ESRI ArcGIS Visual Basic 6.0 applications to .NET
      • Drag and Drop Conversion Steps
      • Inserting elements in a ListView
      • String vs StringBuilder
      • Word Automation in VB6 vs .NET
      • Configure default Factory Database provider
      • GetPrivateProfileString Windows API working in migrated code
      • Upgrade projects with shared files
  • Release Notes
Powered by GitBook
On this page

Was this helpful?

  1. Issues and Troubleshooting

Running a .NET Core application in a machine with no Visual Studio installed

PreviousVB6 On Error StatementsNextDatabases issues

Last updated 4 years ago

Was this helpful?

When you want to run a .NET Core application in a different machine where it was created you will need to install the Runtime to be able to execute it, but in some cases when you migrate an application using the VBUC tool and you try to execute it in a different machine you can get an error like the next one.

To fix the previous error, you need to click on the "yes" option on the displayed message or you can open the next . There you will see different .NET Core versions to install.

The VBUC tool is able to migrate to .NET Core 3.1, for that reason, you need to choose the same version to download and install the Runtimes.

It is not necessary to install the SDKs to run .NET Core applications.

Once there, you need to choose and download the appropriate version depending on your OS, in the case of Windows, you need to install both (x86 and x64) when you have finished installing the necessary runtimes, you can execute your application again. This problem is commonly related to the platform target used by Visual Studio to compiles a project.

Note: You can check the .NET Core SDKs and Runtimes installed using the command prompt. Once you have opened the command prompt you can use dotnet --info command and a list with the SDK and Runtime versions will be displayed. To run the applications you only need to install the Runtimes.

link
.NET Core error message
.NET Core versions
Necessary options to run .NET Core applications
Platform target to build the project
SDK and runtime versions installed