I am not able to publish to azure my web api, after updated Visual studio 2015 update 3.
The error message says:
The “PublishTelemetry” task could not be loaded from the assembly
C:\Program Files
(x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.Tasks.dll.
Confirm that the declaration is correct, that the assembly and all its
dependencies are available
I have found the fix here. I edited with admin rights, the file
C:\Program Files
(x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets
and removed the tag PublishTelemetry and its using tag. After edition, I restarted visual studio. Now I am able to deploy again.
Even after editing the admin rights it wasn't working so I just install the MSBuild.Microsoft.VisualStudio.Web.targets from NuGet.
I downloaded the MSBuild.Microsoft.VisualStudio.Web.targets package from NuGet and replaced the C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web folder with MSBuild.Microsoft.VisualStudio.Web.targets.14.0.0.3\tools\VSToolsPath\Web folder from tha package.
Related
I am trying to implement a custom code analysis assembly for SSDT. I am following the guide at Walkthrough Authoring a Custom Static Code Analysis Rule Assembly for SQL Server.
After I copy the resulting .dll and .pdb files to the designated directory, the project doesn't load, and I get this error message:
One or more projects in the solution were not loaded correctly. Please see the Output Window for details.
And there is this message in the Output window:
Exception has been thrown by the target of an invocation.
I don't know how to troubleshoot this.
I am using Visual Studio 2017 and an SSDT project that targets SQL Server 2016. So this is the directory I used as the target for the .dll and .pdb files:
\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\Extensions\Microsoft\SQLDB\DAC\150\Extensions
This is the target directory given in the link:
\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\Extensions\Microsoft\SQLDB\DAC\120\Extensions
I've tried only copying the .dll file. I've tried restarting all running instances of Visual Studio as well as restarting the computer. I've tried running Visual Studio with the /log switch and looking for details in the ActivityLog.xml file.
I was developing my WPF projects using Visual Studio 2013 in my old window 7. But when I installed new Windows 10 and also Visual Studio 2017 and tried to open my project; my project fail to load and got this error message:
the imported project "C:\Program Files (x86)\Microsoft Visual
Studio\2017\Enterprise\MSBuild\Microsoft\Expression\Blend.NETFramework\v4.5\Microsoft.Expression.Blend.WPF.targets"
was not found. Also, tried to fiend
"Microsoft\Expression\Blend.NetFramework\v.4.5\Microsoft.Expression.Blend.WPF.targets
in the fallback searchpath(s) for $(MSBuildExtensionsPath) -
"C:\Progam Files (x86)\MSBuild" . These search paths are defined in
"C:\Users\AdminPC\AppData\Local\Microsoft\VisualStudio\15.0_51bebed7\devenv.exe.config"
. Confirm that the path in the declaration is correct , and
that the file exists on the disk in one of the search paths.
C:\Users\AdminPC\Documents\Visual Studio
2013\Projects\MyCustomMessages\MyCustomMessages.csproj
I Searched for some solutions I found I have to install BlendWPFSDKv4_en.msi Version 4, but still doesn't help also there is no BlendWPFSDKv4_en.msi version 4.5. What Should I do, Shall I install VS 2013 in order to fix this issue?
The imported project C:\…\v4.5\Microsoft.Expression.Blend.WPF.targets" was not found
Found it. You should launch the Visual Studio Installer from the start menu, switch to the "Individual components" page, under the "SDKs, libraries, and frameworks" heading, find the "Blend for Visual Studio SDK for .NET" and install it:
After the installation is complete, you will find it under the path:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Microsoft\Expression\Blend.NETFramework\v4.5
Certified:Visual Studio 2017 - What happened to Expression interactions?
Hope this helps.
You can remove the reference to blend;
With VS 2019 - Right click on the (unloaded/load failed) project.
Select - edit your *****.csproj file.
At the bottom of the file, remove the following line
<Import Project="$(MSBuildExtensionsPath)\Microsoft\Expression\Blend\.NETFramework\v4.5\Microsoft.Expression.Blend.WPF.targets" />
Save, Reload the project & happiness.
I had solved the problem by installing
Install Microsoft Expression Blend Software Development Kit (SDK) for .NET 4,
without install an older version of VS
I had solved the problem by installing VS2015 in the same machine that has VS2017 and now the project works fine in VS2017.
I am having an issue where a C++ project that my application references is not being loaded at runtime (i.e. I get an "file or assembly not found" exception). After trying many different things I stumbled onto the click once prerequisites menu and noticed that there was a number of prerequisites with the yellow error sign beside them.
I am not sure if this will resolve my "assembly not found" exception or if I am going down the wrong path, but I figured I'd ask. Why does Visual Studio not find these prerequisites on my machine??
I have searched in some folders like C:\Program Files(x86)\Microsoft Visual Studio 14.0\SDK\Bootstrapper\Packages but I don't think this folder contains my prerequisites (though I am not 100% sure what to be looking for in these folders), instead it contains to more folders called SqlClrTypes_x64 and SqlClrTypes_x86.
I am using Visual Studio 2017 on a Windows 10 64 bit machine.
Does anybody have any ideas on why visual studio cannot find the prerequisites in the image below?
In Visual studio 2017, all packages stored on C:\Program Files (x86)\Microsoft SDKs\ClickOnce Bootstrapper\Packages path are only visible in prerequisites list.
In your case, those packages are added from machine which has those packages at above location.
You might have to create custom packages for above files, like given in the example below link:
https://learn.microsoft.com/en-us/visualstudio/deployment/creating-bootstrapper-packages?view=vs-2017
I have installed VS2017 and call
call "%VS120COMNTOOLS%VSVars32.bat"
from the command line but all I get is
'"%VS150COMNTOOLS%VSVars32.bat"' is not recognized as an internal or external command, operable program or batch file.
If I run "set" from the command line I can see VS120COMNTOOLS (for VS2013) & VS140COMNTOOLS (for VS2015) but there is no VS150COMNTOOLS. How can I build from the command line?
I submitted this as a tech support issue to Microsoft who accepted it as a bug in the install ("there is no VSVars32.bat in the C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\Tools directory.").
However, there is a work-around:
From MS:
At least, since there is a VsDevCmd.bat, there is a Visual Studio 2017 Developer Command Prompt, which also sets, modifies environment variables (Framework40Verion, FrameworkDir, FrameworkDIR64, FrameworkVersion, FrameworkVersion64, INCLUDE, IPCPATH, PATH, VCINSTALLDIR, VCToolsInstallDir, ...)
C:\Program Files (x86)\Microsoft Visual Studio\2017\EDITION\Common7\Tools\VsDevCmd.bat
Run C:\Program Files (x86)\Microsoft Visual Studio\2017\EDITION\Common7\Tools\VsDevCmd.bat where EDITION is the type of VS2017 install, i.e. C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\Tools\VsDevCmd.bat for the Enterprise install. This sets up the needed environment variables and batch builds will work.
Hope this helps anyone struggling with the same issue.
VS2017 has reworked its directory structure and filenames. The file is no longer titled "VsVars32.bat", you should look for the file 'vcvars.bat', which can be located in ..\Program Files (x86)\Microsoft Visual Studio\2017\EDITION\Common7\Tools\vsdevcmd\ext\vcvars.bat (using Adam's syntax, replace EDITION with the version of Visual Studio you use).
For simplicity, you can use %VSAPPIDDIR% in your call to point to the IDE folder where devenv.exe is located, and go back one folder to define your path to the batch file. For example:
call "%VSAPPIDDIR%..\Tools\vsdevcmd\ext\vcvars.bat"
If its any help to anyone...
If you modify your Visual Studio 2017 installation to install the component:
"VC++ 2015.3 v140 toolset for Desktop (x86,x64)"
then the 'VSVars32.bat' file which is missing, will be installed (as its a component of VC++ 2015, but not VC++ 2017).
I've been stuck in this for a couple of hours.
I want to deploy my C# application using a Visual Studio ("Windows") Installer instead of a Click Once Installer.
For doing that, I had to install an extension called "Visual Studio 2015 Installer Projects", which I did.
But once I finally created the setup project for my solution, when I try to build it, I get the following error:
"Sign tool was not found at path: C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin\signtool.exe"
I checked that in fact, signtool.exe isn't there. But after a little research I found that signtool.exe is located under:
C:\Program Files (x86)\Windows Kits\10\bin\x64 and
C:\Program Files (x86)\Windows Kits\10\bin\x86
No here's is my question: how do I tell Visual Studio where the signtool.exe is located? is it a global, visual studio configuration or a project specific configuration?
Thanks in advance
You can use environment variable WindowsSdkDir. For example in command line:
"%WindowsSdkDir%bin\x64\signtool.exe"
or within msbuild script:
$(WindowsSdkDir)bin\x64\signtool.exe
instead of x64 you can use x86 if you use 32-bit windows version
I believe, will be much better to add
C:\Program Files (x86)\Windows Kits\10\bin\x86
path to the global system path (via ControlPanel->System->Advanced system settings->Environment variables...