I have a Visual Studio solution with a few ASP.NET projects. I want to install OctoPack on some of them. So far I have been able to install OctoPack on one project, but not on the others. What can be the reason?
I have installed System.Runtime.Serialization.Primitives and then I could install OctoPack.
Related
I installed the Visual Studio 2017 Enterprise and updated it to the last version. I choosed the necessary web components in the Visual Studio Installer, tried to execute the devenv /InstallVSTemplates, tried to repair Visual Studio and installed .NET Core SDK (x86 and x64).
Nothing of this helped me, I still can't find the ASP.NET Core Application under .NET Core in Visual Studio. How can I solve this problem?
Solution that I found myself: Everything described above was indeed caused by a mistake in the third screen.
I did not find how to solve this problem automatically, I just installed all these .msi packages manually. The installer loads them, but for some unknown reason can not install it themselves. To install them manually, you need to go to the directory where Visual Studio is installed, there just look for these packages by name and install them. Then you need to run the installer again and if it shows another error with another package, you need to repeat the procedure with a manual installation. I had to repeat it three times with three different packages. After that, I started the installer once more and it installed the rest.
What is the workflow when developing VSIX extension? Should I uninstall and install extension each time I rebuild the project, or is there any easier way to do this?
Is it possible somehow to rebuild it and see the changes without uninstalling it and installing again?
Add the solution:
Like Simon Mourier's suggestion, for the VSIX project, you don't have to uninstall it if you want to update it. It would cover the previous project automatically during you run the latest version.
On one machine, I don't have the Web Projects.
First of all I had a Ultimate Trial, there I had the webprojects. Then I uninstalled it and installed the Professional, since then all web projects (4.5 and 5 rc) are missing.
I did install the Web Developer Tools. I Also installed and repaired the asp 5.
I also uninstalled VS2015 and reinstalled it.
On all other machines even those where i also uninstalled the ultimate it works fine I don't want to reinstall the whole machine :-/
Try to reset to default templates back by using the following command line (run as local Admin):
devenv /installvstemplates
UPDATE: also removing folders ItemTemplatesCache and ProjectTemplatesCache from C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE might help. It is pretty safe to delete them but I would backup just for any cases.
i've been working on a ASP.Net mvc5 project and been using TFS as my Version control. Been going great up until now when I formated my computer to Windows 10.
I have a couple of references that didn't work, so I need to restore them.
I know I can use the following nuget command Update-Package –reinstall how ever using that doesn't work as I want it to. It does not restore all the packages such as System.Web.Mvc How can I fix this?
You need to update or re-install your .net Framework.
I have many .sqlproj projects that need to be built on our build server. I don't want to install all of Visual Studio on the build server just so I can install SSDT to build these. How can I build .sqlproj projects without a full VS install?
Here's the raw error I get on the build server when trying to build without SSDT intstalled:
C:\MyProject\MyProj.sqlproj (4): 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 <Import> declaration is correct, and that the file exists on disk.
Answer: Microsoft now has an official NuGet package (see blog post).
Old answer, prior to August 2016; provided in case the NuGet package doesn't work for you:
Install dacframework.msi (x86|x64)
Install SQLDOM.MSI (x86|x64)
Install SQLLS.MSI (x86|x64)
Install SQLSysClrTypes.msi (x86|x64)
Install SSDTBuildUtilities.msi (from the "Administrator Install Point" as setup in step 3 here)
Done!
Source: Headless MSBuild Support for SSDT (*.sqlproj) Projects.
Microsoft SQL Server Data Tools:
http://msdn.microsoft.com/en-us/data/hh297027
Install the tools on build machine to fix the problem.
The Microsoft SQL Server Data Tools team has released a NuGet package named Microsoft.Data.Tools.Msbuild, which helps to build SQL Projects on build servers.
see : https://blogs.msdn.microsoft.com/ssdt/2016/08/22/releasing-ssdt-with-visual-studio-15-preview-4-and-introducing-ssdt-msbuild-nuget-package/
NuGet package : https://www.nuget.org/packages/Microsoft.Data.Tools.Msbuild/
SSDT v12.0.50730.0 requires Visual Studio to be installed beforehand. I found the easiest solution was to install the bare minimum Visual Studio components which were downloaded from MSDN Subscriber downloads:
Visual Studio 2013 Isolated
Visual Studio 2013 Shell
Then SSDT installed fine.
I also used part of the solution outlined above.
* Install dacframework.msi
* Install SQLDOM.MSI
* Install SQLLS.MSI
* Install SQLSysClrTypes.msi
I use MSBuild 12.0 to perform the build which is also available as a separate download.
I was having the exact same issue building a SQL Server project on an Azure DevOps CI/CD pipeline. None of the pre-built build tasks would work for me.
Some answers mention a NuGet package, but I am not sure how can I use it, because SQL Server projects do not allow to install NuGet packages.
I solved this by avoiding to add a SQL Server project to the solution.
I achieved this by using an MSBuild SDK, capable of producing a SQL Server Data-Tier Application package (.dacpac) from the set of SQL scripts. By adding this second project to the solution, I managed to continue taking advantage of linking the project to a live database through SQL Server Object Explorer on Visual Studio. I gave a more detailed explanation about my implementation in this answer.