Refer to Installation of AnkhSVN Visual Studio 2019, although it can be successfully installed, it still cannot be used in visual studio 2022
ActivityLog.xml:
CreateInstance failed for package [AnkhSVN - Subversion Support for Visual Studio]Source: 'mscorlib' Description: Could not load file or assembly 'file:///c:\users\xxxx\appdata\local\microsoft\visualstudio\17.0_1d0575ca\extensions\mhbmk1bf.g1d\Ankh.Package.dll' or one of its dependencies.
According to the authors it will be on the Market place soon. For now use the direct installation link (uzip and execute). https://github.com/AmpScm/AnkhSVN/releases/download/v2.9.87/Ankh-VSIX-2022.zip
The version linked in the Gutek answer (https://github.com/AmpScm/AnkhSVN/releases/download/v2.9.87/Ankh-VSIX-2022.zip) don't work well with Visual Studio 2022, when opening VS2022 it gives several errors (https://github.com/AmpScm/AnkhSVN/issues/44)
At the moment, for Visual Studio 2022, they recommend to install the latest version built correctly and is available in https://github.com/AmpScm/AnkhSVN/actions (the vsix are in the artifacts of a successfully build)
From the extension page, AnkhSVN does not support visual studio 2022. And I suggest you can leave this question here: AnkhSVN - Subversion Support for Visual Studio Q&A
Related
I am trying to install GitHub Copilot in Visual Studio for Mac as an extension. However, there is no option "Manage Extensions" in VS for Mac as shown here.
Is it possible to add it somehow?
As mentioned in the comment, As of now (Nov 2022) this feature is not yet released for Visual Studio Mac. You can also follow this Github discussions
In my Visual Studio Extension for VS 2019, I am currently using Visual Studio SDK version 16.0.202. This is the oldest version with Major Version 16.
If I update the version of the Visual Studio SDK, for example to 16.10, will that require users of my extension to update their version of Visual Studio as well?
Put another way, if I want my extension to support all versions of Visual Studio 2019, do I have to have to stay with the 16.0 version of the SDK?
It is a good question, but I would be surprised if this is true. The libraries provided by Visual Studio, for your purposes specifically (extensibility), shouldn't change the major version numbers. Over the years, I have created many versions of visual studio packages, and I never had this problem. I always use the latest version of the SDK available, since they are actively fixing bugs. However, they may always screw up. Also, if you use internal Visual Studio libraries, not for extensibility, all bets are off.
Qt Visual Studio Tools 2.3.0 has recently been released but isn't recognised by Visual Studio 2019. Does anyone know if it can be modified/rebuilt for VS2019 or when support might be added?
Support for VS2019 has since been added and will be available in the next version of the Qt Visual Studio Tools, which is scheduled to be released in a few days' time.
I recently switched to using Visual Studio Enterprise 2017. My solution builds just fine in Visual Studio Enterprise 2015, but when I try to build in 2017 I get an error.
Output window says:
At
C:\Repos\...\MyProject\_CreateNewNuGetPackage\DoNotModify\New-NuGetPackage.ps1:1206
char:7
"Could not determine where NuGet Package was created to. This
typically means that an error occurred while NuGet.exe was packing
it..."
Things I tried:
updating all Nuget packages to most recent version
deleting the solution and pulling it down from git again
Restoring Nuget packages ("All packages are already installed and there is nothing to restore")
Are there still some bugs in Visual Studio 2017, or do I need to update something with Nuget?
At C:\Repos...\MyProject_CreateNewNuGetPackage\DoNotModify\New-NuGetPackage.ps1:1206 char:7
"Could not determine where NuGet Package was created to. This typically means that an error occurred while NuGet.exe was packing it..."
According to the error log, you can check the NuGetPackage.ps1 file, you will noticed that the parameter of $ProjectFilePath or $NuSpecFilePath is needed.
Besides, in the Visual Studio 2017 release note:
MSBuild support for .NET Core projects, with a simplified csproj
project format that makes it easier to edit by hand, without the need
to unload the project.
And in Visual Studio 2017, the NuGet 4.0 will be shipped as a part of Visual Studio. So when you have custom build task in the your project, you need to check the NuGet version and the parameter of ProjectFilePath or NuSpecFilePath.
If above could not help you, you can share your project file to us, we will follow it up.
Hope this can help you.
I am using the latest version, 1.0.82.0 (sqlite-netFx40-setup-bundle-x86-2010-1.0.82.0.exe), and am using the released version of Visual Studio 2012 with all the latest everything.
I do not see the SQLite in the Designer Data Source in Source Explorer (new Connections).
The download on SQLite states, "This setup package is capable of installing the design-time components for Visual Studio 2010". I presume the "Visual Studio 2010" part is why I do not see the designer in VS2012, which is what I have.
How can I get the designer to work with VS2012?
When will the System.Data.SQLite.org team come out with a version that works with VS 2012?
(I did see a couple of posts back in July which talked about 1.0.66 and 1.0.73, but that was then and 1.0.82 includes the designers just for VS 2010 apparently. I see other file names with "-2008" presumably for Visual Studio 2008. That means that a Visual Studio 2012 will probably come, but in the mean time, I am curious about a manual registry hack or something like that.)
In order to get designer support for SQLite in Visual Studio, you have to download a very specific version of System.Data.SQLite. The downloads page has an astonishing 56 different possibilities, so it's easy to get the wrong one.
Look for the big bold text that says this:
This setup package is capable of installing the design-time components for Visual Studio 2012.
But it's still easy to miss among the zillions of downloads. If you need to, use Control-F to find the "Visual Studio 2012" text.
Don't download the 64-bit version, even if you're on a 64-bit machine. You need the 32-bit version with the text above to get designer support.
NEW EDIT NOW I GOT IT WORKING!
Goto Visual Studio, Manage Nuget, search for online packages, search "SQLite", install System.Data.SQLite, and boom, you can use designer and evrything is working again.
After some search I found my answer, 1.0.83, which will come out in November XX, 2012.
Visual Studio 2012 aside from the v10 to v11 registry hive difference also has what the team calls a "redesigned designer support".
Here is the link to the information.
http://system.data.sqlite.org/index.html/doc/trunk/www/news.wiki
1.0.83.0 - November XX, 2012 (release scheduled)
•Updated to SQLite 3.7.15.
•Add Visual Studio 2012 support to all the applicable solution/project files, their associated supporting files, and the test suite.
•Add Visual Studio 2012 support to the redesigned designer support installer.
and other changes.
I could not find any interim solution on the web, sadly. The lack of a fix affects report based projects with DevExpress and projects that use the explorer.