The application has failed to start because its side-by-side configuration is incorrect.
I guess you are lacking the Visual Studio 2005 C/C++ runtime libraries (Version 8.0) to be installed on the system. You need to install the appropriate vcredist_x64.exe package which can be downloaded from Microsoft.
Related
I have a .NRY Standard 2.0 Project with a class library where I use the System.DataODBC (installed as Nuget Package) to connect to an Access mdb file.
I then wrote a .Net Framework 4.7.2 console app to test the library and that works as expected. I then wrote a .Net Core 3.0 console app, because the app that in the end will be using the library is a .Net Core app. But this didn't work I get this error:
ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
But I then tried to compile the solution with "x86" instead of "Any CPU" - And that works. I then think it must have something to do with the ODBC driver for 32 of 64 bit?
To be clear I haven't configured any ODBC driver with ODBC admin (odbcad32.exe). I can now run the core Console App in Visual Studio and stand-alone.
But when I put the Core Console app on another machine (a clean install Windows 10 pro in a VM) it still won't work.
What do I have to do/install in the VM machine to get it up running?
If you use mdb (the older legacy JET engine), then you can connect on any machine since a copy of the JET database is shipped with each copy of windows. And YES, you will have to force your project to x32 (x86) since the JET data engnie is only available in x32 versions.
If you use ACE, then you are using the newer ACE data engine which is require if you use the Access 2007 and later format (so for accDB files, you MUST use ACE).
Of course like any drivers or software, if you going to deploy to additional machines, then you have to ensure that ACE is installed. As a general rule, you then have to (should) install the access connectivity components. eg this one:
https://www.microsoft.com/en-us/download/details.aspx?id=54920
Keep in mind that there are two versions of the above. A x64 bit version, and a x32 bit version. You want to continue to FORCE you .net project to x32 or x64, since you can't leave this choice to the wind.
So, you have to include the above install as part of your installer, or simply provide a copy, or have users download + install.
The only way to eliminate the need for above is to go with JET, but that may not be a possible choice for you, and you are restricted to mdb files, and can't use accDB files with JET.
Thanks for the quick answer.
But I found that to run a .Net core app using the System.Data.ODBC the app heve to be compiled for x86 CPU and the server where the app is installed needs to have the .Net Core runtime 32-bit version installed.
UWP App not being able to work with MySql
I have made an app in UWP and instead of using SQLLite which seems to be the norm for Visual Studio 2015 I want to use MySql. I have already connected my Azure mysql database to Visual Studio via the 'Server Explorer'.
I'm using MySQL Workbench to update my tables within my connected database from Azure but I cannot actually write any code to access my tables as whenever I try to install MySql.data/.entity/etc in the NuGet Package Manager I get an error.
nuget error
I tried downloading the Mysql installer, the Mysql drivers for Ado and ODBC. I even tried downloading the MySql for Visual Studio option as I found out that Visual Studio is not compatibile with MySql and instead requires the MySql for Visual Studio download but I still have errors whenever I try to use MySql in my code as I need an assembly reference for it but I'm having no luck in being able to get one that doesn't error.
Does anybody have any idea how I could actually use MySql within Visual Studio 2015?
This is what I've been using as my guideline but I can't seem to get past the Mysql.data errors when installing.
http://web3.codeproject.com/Articles/1074242/Designig-your-Azure-MySQL-DB-with-a-UWP-Demo
I have seen a lot of people talk about this but there is no one straightforward fix (I've tried a lot of the fixes, one in particular being to use Vs13 to install Mysql in the Nuget package manager and then it should update within VS15 but as my app is a UWP VS13 does not actually load/read it so that idea isn't good to me, might help anyone else though)
Starting with 6.7, Connector/Net fully supports building Windows Store apps. But using Connector/Net RT is not by install the Nuget package, it just reference the MySql.Data.RT.dll assembly according to MySQL Connector/Net Developer Guide:
Using Connector/Net RT is easy. Simply create a Windows Store application using Visual Studio and then reference the MySql.Data.RT.dll assembly in your project. The code you write should be exactly the same as for normal Connector/Net (including using same namespace MySql.Data.MySqlClient) except for the differences listed above.
You may find this dll at C:\Program Files (x86)\MySQL\Connector.NET 6.79\Assemblies\RT if you have install the connector. You can also download the mysql-connector-net-6.7.9-noinstall.zip to find this file inside the folder. I also have a MySql UWP sample before and has the dll here. Right click your project and add reference for this it will work.
More details please reference this sample
I recently installed Visual Studio 2013 Professional, after install VS I installed MySql for VisualStudio version 1.2.6 that it is the latest release. The problem is when I tried to create a ADO .Net Entity Model I created the connection perfectly fine but when I press Next the window close it self and Visual Studio doesn't create the model.
Things that I checked:
I already have installed in my project the Entity Framework 6, MySQL.Data V6.9.8, MySQL.Data.Entity.EF6 v6.9.8 and MySql.Web v6.9.8.
In the Visual Studio Private Libraries there there is the three same libraries with the same version.
I checked other posts here and I really don't find the cause of my problem. I will be very grateful with any help.
Edit
I attached the process to another instance of Visual Studio and I got this:
'devenv.exe' (CLR v4.0.30319: ProjectExecutionContextDomain): Unloaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Numerics\v4.0_4.0.0.0__b77a5c561934e089\System.Numerics.dll'
'devenv.exe' (CLR v4.0.30319: ProjectExecutionContextDomain): Unloaded 'C:\Users\Jose\AppData\Local\assembly\dl3\3C4YP8TT.W35\4414OC0M.0ZV\4aeb0621\323bbd39_5088d101\SignaSafePro.dll'
'devenv.exe' (CLR v4.0.30319: ProjectExecutionContextDomain): Unloaded 'C:\Users\Jose\AppData\Local\assembly\dl3\3C4YP8TT.W35\4414OC0M.0ZV\77badc31\29b0d95d_4088d101\EntityFramework.SqlServer.dll'
'devenv.exe' (CLR v4.0.30319: ProjectExecutionContextDomain): Unloaded 'C:\Users\Jose\AppData\Local\assembly\dl3\3C4YP8TT.W35\4414OC0M.0ZV\27b7b188\7ad46db4_4f88d101\MySql.Data.Entity.EF6.dll'
A first chance exception of type 'System.ArgumentException' occurred in System.Data.dll
A first chance exception of type 'Microsoft.VisualStudio.TemplateWizard.WizardCancelledException' occurred in Microsoft.Data.Entity.Design.dll
The thread 0x908 has exited with code 259 (0x103).
I also uninstall and install all again, the libraries references are exactly the same, because I'm reference the libraries from the PrivateAssemblies folder.
Guys thank you very much, the problem was my mistake, I thought if I installed just MySQL for Visual Studio was enough but I didn't realized that the MySQL Connector is needed to:
MySQL Connector/Net Developer Guide
I hope it serve to guide for anyone other like me.
Requirements
Windows OS 7 or later.
Visual Studio 2010, 2012 or 2013 Professional or higher version.
Connector/Net 6.8.1 beta or higher version (MySQL Connector download link).
Additional download links (not required)
MySQL for Visual Studio (latest version)
i downloaded the recommend version from Download MySQL Community Server i.e mysql-installer-community-5.6.12.0.msi for windows 7 64 bit os.
Please install the .NET framework 4. Please install the .NET framework
then run this installer.
My question is Should i really install .net 4 framework first to install mysql server? Am i proceeding in right direction
The standard installer includes MySQL Workbench. If you look at its download page, and in the pre-requisites:
To be able to install and run MySQL Workbench 5.2 your System needs to have libraries listed below installed. The listed items are provided as links to the corresponding download pages where you can fetch the necessary files.
Microsoft .NET Framework 4 Client Profile
Microsoft Visual C++ 2010 Redistributable Package (x86)
So, yes.
(There may be other packages that also depend on .NET. Workbench was the obvious one I know of)
When I click on EDIT SCRIPT button for Script Task in SSIS 2012 package,
It does not open the Script editor rather it shows:
"cannot show Visual Studio Tools for Application editor"
Couls not load file or assembly
"Microsoft.visualstudio.tools.applications.core version=10.0.0.0 ...."
system can not find the file assembly specified.
I tried the solutions provided in the following links:
http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/e5337b0c-7f70-4603-859e-fbc7d0cf1c37
SSIS Script Editor throws an exception
First of all go to Program and Features and check whether you have
"Microsoft Visual Studio Tools for Applications x86 Runtime 3.0"
installed. Most probably you will see this below
"Microsoft Visual Studio Tools for Applications x64 Runtime 3.0"
If it is not installed then you have the same issue that i have.
To resolved this error, I put in my SQL Server installation disk. Then go to redist->VSTA->runtime->x86 and then run VSTA_RT30.msi
The workaround mention in this link solved my issue:
https://connect.microsoft.com/SQLServer/feedback/details/776248/could-not-load-file-or-assembly-microsoft-visualstudio-tools-applications-core
Both the x86 and x64 runtimes must be installed, currently one or both the runtimes may be missing depending on the order of the SQL Server 2012 installation. As a workaround, check in Control Panel - Programs and determine which of the component is missing (it should be listed as Microsoft Visual Studio Tools for Applications x86 or x64 Runtime 3.0). You can install the component manually from your installation disk or download from the \redist\VSTA\runtime\ folder.
It is year 2021, when searching for the error, this is the top hit. The solution that worked for me with Visual Studio 2019 is to download and install "Visual Studio Tools for Applications 2019"
Link:
https://www.microsoft.com/en-us/download/details.aspx?id=58317&WT.mc_id=DX_MVP4025064
Interestingly, this is not provided as an option in Visual Studio installer. The above needs to be manually downloaded and installed.
By now, SQL Server 2012 Service Pack 1 is out. Try updating your release and after that, you might even consider putting the Cumulative Update 1 on top of it.
More about CU1: http://blogs.msdn.com/b/sqlreleaseservices/archive/2012/11/21/cumulative-update-1-for-sql-server-2012-service-pack-1.aspx
goto SQL server installer folder and install these msi files
redist/VSTA/designtime/VSTA_DT30msi
redist/VSTA/runtime/x64/VSTA_RT30.msi
redist/VSTA/runtime/x86/VSTA_RT30.msi