cancel
Showing results for 
Search instead for 
Did you mean: 

Visual studio integration

Former Member
6,293

Hi, I'm hoping some one has encountered this before. We are running Sybase 12 (installed in c:asa12) we have both 64 and 32 bit versions installed. When opening the server explorer tab in visual studio we get an error stating that the Sybase package failed to load, it then suggests checkingbthe activity log.XML file for VS which gives us the guid of the package and not much else.

Until now this has not been much of an issue as we just avoided usingbthat dialogue, however now we need to do some work with EF and could really do with getting in this working.

Please note when I say we, there are 4 of us with the same issue... So its not just something that I have screwed up!

Hoping that some one may have some ideas as to what could cause this, or some way that we can shed some more light on what the issue is?

Thanks in advance.

Accepted Solutions (0)

Answers (3)

Answers (3)

jeff_albion
Product and Topic Expert
Product and Topic Expert

Hi David,

CreateInstance failed for package [SQL Anywhere explorer]

Ahhh, that's somewhat more clear. Although, this is a component from SQL Anywhere 11 not 12 (as the SQL Anywhere Explorer was removed in 12.0.0). Did you also have SQL Anywhere 11 installed previously (or was it installed as a component as part of your fresh install)?

The SQL Anywhere Explorer was actually a component that was slowly deprecated throughout the course of 11.0.1. It was only briefly supported in Visual Studio 2010, and then 2010 support was dropped as of 11.0.1.2257 and higher (see: CR #576252). Visual Studio 2005 and 2008 support was also eventually dropped as of 11.0.1.2456 (see: CR #637453). The component was never considered for Visual Studio 2012 though, so I'm not 100% why you're seeing it even loaded here... particularly if this is a clean install. Are you loading previous Visual Studio settings when you're migrating...?

I believe you should just be able to disable/remove the SQL Anywhere Explorer extension by going to "Tools" → "Extensions and Updates...", click on the extension "SQL Anywhere Explorer" and click "Disable" or "Uninstall".

Former Member
0 Kudos

One other update, this is the details for the DLL in the Assemblies directory in the SQL Anywhere 12 folder: http://1drv.ms/1esZ3ou

So it all looks like its v12, further to that when I run the set up it explicitly states that its installed for VS 2010 & 2012:

Console Output:

C:Program Files (x86)SQL Anywhere 12Assemblyv4>SetupVSPackage.exe -i iAnywhere Solutions (R) SQL Anywhere Package for Visual Studio .NET Setup Utility Version 12.0.1.38402 Copyright (C) iAnywhere Solutions 2008. All rights reserved Installing SQL Anywhere Package for Visual Studio 2010...... Succeeded Installing SQL Anywhere Package for Visual Studio 2012...... Succeeded C:Program Files (x86)SQL Anywhere 12Assemblyv4>


Of course I have to now uninstall it again if I want to use VS Server explorer to connect to any other databases... 🙂

g_g_99
Participant
0 Kudos

albeit quite a late but one could try microsoft odbc instead in server explorer using user of system dataset. I know it worked for for me with vs2017, 2013

Former Member
0 Kudos

Hi,

Neither my laptop or the virtual machine that I set up for this test have ever had v11 installed, the VM that was set up was literally done by pressing next on every step of the VS and Sybase installers without changing anything and no previous settings were imported into VS after the install, so what I am seeing seems to be the default behaviour out of the box.

Details of the MSI that I have installed here : http://1drv.ms/1esVlva and as you can see here it does not show in the tools - extensions & updates : http://1drv.ms/1cRRgWG

Anyway, if this is correct and it should not be available in 12 thats fine, do you know if it has been replaced with anything? We would like to use EF to provide the DAL for our application and would like to use some of the built in tools in VS which all share this dialogue so dont work!

If you have any insights into this it would be greatly appreciated!

Thanks David