Visual Studio Express 2013, new installation wont launch - The application has failed to start because its side by side configuration is incorrect - configuration

I tried installing Visual Studio 2013 Express for Desktop for the first time ever as I'm trying to get in to C# as Python doesn't really meet my needs. The installation ran fine, as I downloaded the ISO and mounted it to a virtual BD-ROM drive when the normal EXE wouldn't work. But now, when I go to run the program it tells me that:
The application has failed to start because its side by side configuration is incorrect.
and doesn't allow me to run the program. I tried to run the installer again to repair the program but it basically reinstalled the whole thing and did nothing. Any help?

Related

SSIS destination component failing due to current version of the data flow

I have a working SSIS package. It works from vs, meaning it builds and executes as expected producing results in the CRM.
After I get the generated .ispac file and deploy it in MSSQL server, I fail on executing.
I get an error that looks like this:
Test Package:Error: Microsoft.SqlServer.Dts.Pipeline.ComponentVersionMismatchException: The version of Create Records is not compatible with this version of the DataFlow. [[The version or pipeline version or both for the specified component is higher than the current version. This package was probably created on a new version of DTS or the component than is installed on the current PC.]]
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostCheckAndPerformUpgrade(IDTSManagedComponentWrapper100 wrapper, Int32 lPipelineVersion).
The aforementioned 'Create Record' is the 'Dynamics CRM Destination' component.
There are many who have such issue, I searched the web, but what all suggest is that we change the target version of the MSSQL server from VS, but I tried that and it doesn't work.
Additional information:
System: Windows 10 pro
VS: 2015
MSSQL: 13.0.6300.2(so it's sql server 2016)
Kingsway version: v21.2(21.2.0.31501)
The 'TargetServerVersion' is set to: 'SQL Server 2016'
What have I tried ?
I have tried to deploy straight from VS, but no luck there.
I ran the same(separately built) SSIS on my local machine where I have vs2019 and sql server 2019, it works fine in here.
I tried to build the project in vs2019 on the main machine and I'm still getting the same error.
So, do you have any idea what's happening, can you give me some advice ?
Thank you for the question about our integration toolkit. To use any of our toolkits for deployment and scheduled execution, the same version should be installed in possibly three places:
On your development machine (this is generally covered by our free Developer license)
On your SSIS Integration server
On the machine which is used to deploy your SSIS packages to your Integration server (if different from your development machine)
Based on the error message, it is either that you didn't install our Dynamics 365 toolkit or otherwise the installed version on the server is lower than what you have installed on your development workstation.

MySQL workbench failing to download

I have a Mac and use parallels to access Windows 11. I am trying to download MySQL, and everything successfully downloaded except for the Workbench. It fails to install every time with the error, "The processor is not adequate for running MySQL Workbench 8.0 CE."
I have tried googling and searching through forums and videos, and cannot find this exact error, and have tried using solutions from similar workbench issues.
I have tried uninstalling the program, and reinstalling, as well as restarting Windows and the computer as a whole. I have downloaded Visual Code 2022, 2019, and 2017 in hopes that one of these would work, but none did. I also added the development C++ add on to Visual Code like some people suggested, and that did not help. I also have downloaded the 2017 Visual C++ Redistributable for Visual Studio 2017 (version 15.9) and tried to "repair" it. Still did not work, still get the same error. Also, I have already downloaded NET framework 4.5, so that is not the problem either.
I don't know where else to look, or what other resources to try and was wondering if anyone had any ideas or knows to how to solve this issue. Thank you for any help!
Windows on ARM emulation isn't good enough to trick the MySQL Workbench installer into thinking that it's running on an Intel CPU, so the installation fails.
Fortunately, this is fixable with some degree of effort - you have to patch the MSI file. There's likely other ways to do the patch, but here's how I did it using Orca:
Install the Visual Studio 2022 ARM preview and include the tools needed for C++ development. This will get the Windows SDK installed.
Run the Orca installer that's bundled with the Windows SDK (it will be put somewhere like "C:\Program Files (x86)\Windows Kits\10\bin\WINDOWS SDK VERSION\x86\Orca-x86_en-us.msi")
Download the MySQL Workbench .msi installer from https://dev.mysql.com/downloads/workbench/. Do not use the MySQL Installer that handles everything - you want the dedicated installer that handles just Workbench.
Right click the downloaded .msi, choose "Show More Options" and then "Edit with Orca"
Open the "LaunchCondition" table in the left hand list.
In the right hand side, there will be a row saying "Intel >= 5". Right click it and select "Drop Row" to remove the CPU check.
File > Save As and save your modified .MSI file.
You can now run the modified .MSI file and it'll install Workbench just fine on your Windows 11 on ARM environment. It works great in Parallels on my M2 MacBook Air!
your Mac silicon is M1?
M1 not support, intel is ok

Visual studio 2013 deploying sql server 2008 database project

I have recently migrated my visual studio 2010 projects to 2013 but my database project looks unhappy about it. I have a TFS build definition which helps me deploy the database project and i have specified the (.sln) solution file and the .proj separate file which helps e drop the file to some location. This has been working well when I was using 2010 but right now its giving me the following error.
The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\SSDT\Microsoft.Data.Tools.Schema.SqlTasks.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.
I replaced .sln file with the .sqlproj and this seems to fix the failing build definition but I don't get any deployment files.
Do you have any suggestions please, this is blocking my work right now.
You need to set the environment variable VisualStudioVersion=12.0 when building from the command line if you are using VS2013. SQL Projects rely on this to detect whether to use the VS2012 (v11.0) or VS2013 (v12.0) targets file when building.
Normally when a new Visual Studio version is released there's an accompanying .Net version update that changes the default VisualStudioVersion default value, but with VS2013 this didn't happen. Hence SQL Projects (and some other resources with similar version-specific dependencies) require 12.0 to be explicitly set as the version, since 11.0 is the default.
Also when running on a build server you must have a version of Visual Studio 2013 installed that includes the SQL Server tools. Full instructions on setting up a build server are in the whitepaper and presentation on the SQL Server tools team blog.

Using Xdebug with Netbeans or Komodo fails when connecting to Mysql

I am trying to get either NetBeans or Komodo IDE to remotely debug PHP. I have a remote website installed on the development machine which is a Mac running Mountain Lion. Xdebug is installed. The website on the local machine runs normally in a browser.
However, for both NetBeans and Komodo IDE, when single stepping through the code, the attempt to execute mysqli_connect fails. In NetBeans there is the following error message:
Socket Exception occured If you have any Watches, try to remove them and restart debugger. If removing Watches does not help or you
don't have any Watches, please file an issue and provide the exact
steps to reproduce your problem. Please attach the IDE log. Attaching
your project would also be very helpful.
I have seen other people reporting this error message, but no help has been provided.
In Komodo IDE, the failure occurs at the same location, but there is no error information provided at all.
The funny thing in NetBeans is that after some single stepping through the first page of the site, if I then run the code from that point, it executes without failure and the web page is displayed in the browser! This means that the problem only occurs while single stepping.
I have seen something somewhere about a bug in NetBeans. But it seems pretty blatant that NetBeans should not be able to single step through code that tries to connect to mysql. Rather I am thinking it would be some configuration issue on my system.
Komodo IDE has the same failure whether single stepping or running any other way. It just does not get past that point.
However, please keep in mind that just running the site in a browser works fine. So what is missing that prevents the Xdebug single stepping from connecting to mysql?
** Additional information **
I have found two instances of xdebug.so on my system.
-rwxr-xr-x 1 root admin 274508 Oct 6 2011 /opt/local/lib/php/extensions/no-debug-non-zts-20090626/xdebug.so
-rwxr-xr-x 1 root wheel 202672 Sep 20 20:01 /usr/lib/php/extensions/no-debug-non-zts-20090626/xdebug.so
Also, there is an /opt/local/var/db/php5/xdebug.ini which references the xdebug.so in the /opt/local path. The xdebug.so in the /usr/lib path is the one that I thought was in use and which corresponds to instructions as to where it should be installed.
These are apparently two different versions of xdebug.so. Could that be related to my problem?
You need to make sure that you are running one version of Xdebug - and also make sure that this is the latest version (2.2.1 at the moment). If you can still reproduce this issue, please file a bug report at http://bugs.xdebug.org with a short sample script (that contains all the code + data!) and a remote debugging log for a debugging session using that script (see http://xdebug.org/docs/all_settings#remote_log on how to make such a log).

Visual Studio Windows Installer with MYSQL check and Install

I have a VB Windows forms application that uses a mysql database to keep track of everything within the application.. The problem that I know will occur is that most of the applications users will not have MYSQL let alone know how to install it properly... To install the application on the users systems I am using the Visual Studio Setup Installer to handle creation of the msi files.. What needs to happen first is the installer needs to check to see if MYSQL is installed on the host system and verify server name.. If true then import database, if not then install followed by import database... The importing is not the issue here... How do I make the installer install mysql with controlled parameters such as server name, etc, etc. Any ideas on this??? I have hammered google for the past 3 hours looking for bread crumbs on this but to no avail...
Usually existing packages (like the MySQL installer) are added as prerequisites. Visual Studio setup projects do not support custom prerequisite creation. However, this can be done by manually generating the required manifests.
You can find the manifests structure here: http://msdn.microsoft.com/en-us/library/ms229223(VS.80).aspx
These manifests can be generated automatically with the Bootstrapper Manifest Generator tool.
After generating the package manifests, you can add all these files (including the package) in a separate folder in the Visual Studio prerequisites folder, for example:
C:\Program Files\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages\
You can then select the prerequisite in your setup project properties page.
Well... that's a good question. The first thing that pops up in my mind:
You could build the check in your application instead of the installer and warn the user about it. If needed, you could provide another installer to make sure everything is available (MySQL and the database itself).
I hope it helps you further.
Yours sincerely,
Roland