I would like to use an ActiveX control, more exactly "Microsoft Tabstrip control, version 5.0 (SP2)" but this is not possible due to license problems.
As mentioned in the answer on this other question, this problem can be solved by installing an old version of Visual Studio (the installation of another environment, using that control, automatically handles the licensing issues of that control, also for other environments, at least that's how I understood it). I have installed the most recent version (2019, 16.8.3), which seems not to be a good idea.
So, there are three ways to proceed now:
Either I uninstall my Visual Studio and replace it by an older version. In that case, which version do I need to use?
Either I add the mentioned control (or ActiveX as a whole) to my list of "Workloads", "Individual Components" ("Tools" menu, "Get tools and features..." menu item).
Either I use the extention handling feature to add (the mentioned) ActiveX control(s) ("Extensions" menu, "Manage extensions" menu item).
Edit after more investigation
In the meantime I've installed Visual Studio 2017, version 15.0, but this seems not to solve the issue. In top of that, I have no idea on how to include an ActiveX control to a basic Windows Form.
Does anybody have an idea?
In the meantime I've managed getting the license to work, installing "Visual Basic 6 (VB6), Service Pack 6".
Related
I am trying to open a C# solution that has been generated from a Unity v2020.3.19f project with Visual Studio 2022. Opening it with Visual Studio 2019 works just fine, but there are reasons I'd like to be able to open it with v2022 (such as GitHub Copilot). I did not have issues with this on my previous install of Windows 10.
Upon opening the solution in VS2022, I get the following pop-up prompt for every project in the solution:
Choosing the first option updates the target project to .NET Framework 4.8 and loads the project, but the whole file appears with red lines. When hovering over an underlined bool Property, the error shows as: `CS0518: Predefined type 'System.Boolean' is not defined or imported.
Choosing the second option opens this URL in my browser, prompting me to install .NET Framework 4.7.1 targeting pack (which was already installed via the Visual Studio Installer). When I try to install the .NET Framework 4.7.1 runtime, the installer responds with .NET Framework 4.7.1 or a later update is already installed on this computer. When I try to install the .NET Framework 4.7.1 Developer Pack, the installer allows me to choose from "Repair", "Uninstall", or "Cancel". Repairing has no effect.
I installed both versions of Visual Studio (2019 & 2022) the usual way through the Visual Studio Installer, along with the "Game Development with Unity" workload, which tells me it's installed all dependencies just fine:
Here's what I've tried so far:
Uninstall & reinstall all versions of Visual Studio through the Visual Studio Installer
Uninstall & reinstall Unity, with the Visual Studio module installed through Unity Hub (which just opens the Visual Studio Installer for me to choose which version I want to install)
Regenerate project files through the Unity Editor
Uninstall any references to .NET Framework through the Control Panel
Try reinstalling .NET Framework targeting pack 4.7.1 either from the Visual Studio Installer or manually through the Microsoft SDK website from the prompt
Nothing works for me. Any help on how to make VS2022 stop complaining is greatly appreciated.
Update 1: I found a couple of threads where people suggested simply pressing the Regenerate project files button in "Edit -> Preferences -> External Tools`. This has not helped me.
Update 2: I've tried everything I can possibly imagine, in different orders and different combinations. I even reinstalled Windows 10 to no avail. It's like Visual Studio just doesn't want to accept that the .NET Framework 4.7.1 targeting pack is installed. Please help :(
check this
https://learn.microsoft.com/en-us/answers/questions/733018/visual-studio-2022-cannot-locate-installed-net-fra.html
If you modified the value of ProgramFilesDir(x86), just to modify it back to C:\ProgramFiles(x86) can solve the problem
That is a very interesting problem, my main solution for you to first try is to make sure you are even targeting the correct .net framework in UNITY before you even build the solution. You are using the .NET 4.x, you need to go into your configuration settings and player settings in unity and ensure its not on a different version, for me, unity still defaults to .net standard 2.0. Follow the steps located here. To do so.
Another solution is to see if that first option actually gives you errors that prevent you from using unity, because I know that Visual Studio Code has problems occasionally where it tells me im wrong, my program is wrong, every life choice I have made was poor and I am poor, yet in unity, there are no errors showing in the console and I can hit play no problem. In that case I just had to rebuild a few times and fiddle with vs code until omnisharp stopped yelling at me.
Apperently I have been in a similar situation as when you were getting the error "Predefined type 'System.Object' is not defined or imported" because looking into it, I already have clicked on some of the links, try this one if that error persists. If you cannot prevent the errors to begin with, I would recommend you trying to fix the upgraded version from option one as that is more than likely going to get you the closest to a solution.
I am using Microsoft Visual Studio Installer projects extension to create an installer for my app.
Works OK, but the problem is that the product name contains "š" character in it and the font used in the msi installer obviously doesn't support that character:
Anything I can do about that?
Some background info:
I initially developed the app in VS 2015 which had a free Install Shield Limited edition. Or maybe it was even VS2013, don't really remember... However, now I need to make some changes in the app. There was no problem with such a name in Install Shield back then. So I tried to open the project in VS 2022, but obviously Install shield's no longer an option. This is where VS Installer project comes in, but there's the problem with the diacritics...
This looks like an encoding issue. Try searching in the VS project properties for an option to set the encoding to Unicode. I don't use the VS projects that much, so I don't know if you have the option to change it not, but it might be there.
Also, if you are looking for a better free MSI packaging tool, try the Advanced Installer extension for Visual Studio. There is one for each version of VS.
Disclaimer. I work on the team building Advanced Installer.
Each time I open Visual Studio Community 2017, I get the dialog below asking about upgrading the version of Microsoft Azure Tools.
This dialog appears 4 times (4 different projects), I click 'OK' each time and then everything seems to work fine. However, next time I open the solution I have to repeat the process.
How do I resolve this once and for all?
Note that this project was created under a different version of VS (likely with a different Azure Tools) but that shouldn't be a permanent issue, I'd think.
That's strange...
Have you tried upgrading the project this way:
In Solution Explorer, open the shortcut menu for the project node, choose Properties, and then choose the Application tab of the dialog box that appears
The Application tab shows the tools version that’s associated with the project. If the current version of Azure Tools appears, the project has already been upgraded. If you've installed a newer version of the tools than what the tab shows, an Upgrade button appears.
This may help as well: https://learn.microsoft.com/en-us/azure/vs-azure-tools-upgrade-projects-to-the-current-version-of-the-azure-tools
I've created a project on VB6 at but when I am opening it on VB8, it shows the following error:
How to fix it?
As listed by GSerg in the comments, this appears to be a known issue documented in Microsoft Knowledge Base article 896292: You receive a "The remote procedure call failed" error message when you upgrade a Visual Basic 6.0 project to Visual Studio .NET 2003 or Visual Studio 2005 on Windows Server 2003 SP1 or on Windows XP SP2
To reproduce the solution here:
Cause
This behavior occurs because the VBU.exe tool has compatibility issues with the Data Execution Prevention (DEP) option.
Note: The VBU.exe tool starts when you upgrade the Visual Basic 6.0 project by using the Visual Basic Upgrade Wizard in the Microsoft Visual Studio .NET IDE.
Workaround
To work around this behavior, add the VBU.exe tool to the DEP exclusion list. To do this, follow these steps:
Click Start, click Control Panel, and then double-click System. The System Properties dialog box appears.
Click the Advanced tab, and then click Settingsunder Performance. The Performance Options dialog box appears.
Click the Data Execution Prevention tab. Verify that the Turn on DEP for all programs and services except those I select option is selected
Note By default, the Turn on DEP for all programs and services except those I select option is selected in Microsoft Windows Server 2003 Service Pack 1 (SP1).
Click Add. Locate and then click to select VBU.exe. Click Open.
In the warning box, click OK. VBU.exe now appears in the DEP program area.
Click Apply, and then click
OK. A dialog box appears that states that you must restart the computer for the setting to take effect. Click OK.
Try do divide your project to small projects(or comment large part of your project) a try again in each small project.
The idea is to find the function that is production the error.
My intuition is telling me that maybe is a DLL or OCX problem. Try to see all the external DLL or OCX calls and remove from the original project and try again the upgrading.
Most developers who move their VB6 projects to .Net do not even try to port them over. Even with third-party "conversion" software, the effort can be incredibly tedious. So much so, that most developers simply re-write the application completely. Consider it a move to a different language. In fact, some developers use that opportunity to port it to C# instead. I'm a die-hard VB6 user/fan but were I to attempt to port my 200 form accounting application, I'd just re-write it in C#. I started porting it, tried third-party conversion apps, just wasn't worth it.
What can I uninstall from this large chunk of programs without breaking Visual Studio Community 2015. I do not use any SQL services or any .NET frameworks for any sort of development, so I don't need SQL or .NET features. Unfortunately VS forced them upon me.
In fact, I only really use Visual Studio to code C/C++ and Fortran, and have no use for its other features.
In search for a solution I came across this cool preview build which would almost exactly be the solution to my predicament, but I need Intel C/C++/Fortran compiler and Intel Visual Fortran (extension for VS) compatibility to be maintained. Intel does not support non-official releases so VS Preview won't do.
Did you install the VS 2015 through the default installation or custom default? If you chose the default installation, those installed items in your first screenshot should be required for the VS 2015, it is better to keep it to make the VS work stable.
If you chose the custom installation, please have a look at the article and it lists the custom components, then you can remove them if you do not need it anymore. To remove them, you can right click the VS 2015 item under Uninstall a program list table and choose Change-Modify, then uncheck the checkbox of those components that you selected in your original custom installation, then the VS installer will auto uninstall those components. Before you try to uninstall any components, I recommend you backup your Windows OS firstly, you can find the backup method per your OS edition search here.
The .NET Framework is required and the basic component for VS, when you try to create any project types in VS, there is a default .NET Framework version like the following: