On an occasion, I found NCrunch was getting stuck at this step when 'NCrunch engine is initialising':
Clean/rebuilds and restarting Visual Studio did not resolve this issue.
To resolve the issue, I closed Visual Studio and navigated to the Visual Studio project folder in the file directory and located the hidden .vs folder and the '_NCrunch _[projectName]' folder and deleted those.
Then I cleaned and rebuilt the solution and NCrunch started functioning again.
I have a VB.NET solution containing multiple projects and the expected result is the EXEs in one project should be copied to bin folder of other projects on build. While rebuild solution does this, build solution does not copy the EXEs and even deletes the previously copied EXEs.
Any idea why this is happening?
Thanks
There provides two method which may help you solve your problem:
1.Renaming the executable file
2.Another method:
Closing Visual Studio
Deleting the bin and obj folders
Reopening Visual Studio.
I'm making windows application in VB.NET and I added some files in my project in solution explorer and I set on every file I added
"Copy to Output Directory: Copy Always"
but it deploy every file except .bin files after publishing.
It work in debugging mode, but not when I publish it. any help please, how to deploy .bin files?
Thanks.
What is the Build Action property of those files set to? If it is Content then I believe that they should be included in the deployment automatically. If not, open the Publish page of the project properties and click the Application Files button. There you can control what files are included in the ClickOnce deployment.
I am getting this error on my CI server:
error MSB4019: The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\WCF\Microsoft.VisualStudio.ServiceModel.targets" was not found
It seems my WCF service library project references that file, but the VisualStudio folder on Program Files\MSBuild\Microsoft doesn't contain a WCF folder.
I guess I need to install something on the server.
What do I need to install?
Well this ruined my morning, but let's not allow it to ruin anyone else's. I couldn't find this information anywhere else. You need to copy a few files from a development machine with VS Pro 2012.
As aphexddb mentions, you need to copy some targets from C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\WCF to the same location on your CI server.
This then references an assembly called Microsoft.VisualStudio.ServiceModel.Core. You can find this assembly in either the GAC or in the IDE directory at C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE.
Copy this to your CI server and execute gacutil.exe -i Microsoft.VisualStudio.ServiceModel.Core.dll
This was enough to fix it for me.
This isn't the first time I found targets missing from my VS express install in my CI server. I can't help but feel that there is some sort of package I can download from somewhere that fills all this in. Does anyone know of such a thing? If not, perhaps we should create one.
Can still happen on vs2019
error MSB4019: The imported project "C:\Program Files (x86)\Microsoft
Visual
Studio\2019\Professional\MSBuild\Microsoft\VisualStudio\v16.0\WCF\Microsoft.VisualStudio.ServiceModel.targets"
was not found. Confirm that the path in the declaration is
correct, and that the file exists on disk.
WCF is not installed by default as part of 'ASP.NET and web development' workload. To fix this,
On visual studio installer > modify > individual components tab, search for wcf, check, modify - the .targets file gets now installed, msbuild builds ok.
MSBuild auto-detection: using msbuild version '16.3.2.50909' from 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\bin'
I ran into this with Visual Studio 2017, for me the resolution was to modify my installation of Visual Studio to include the Windows Communication Foundation components.
Extract this file into folder
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\WCF
The file name is "Microsoft.VisualStudio.ServiceModel.targets"
Now you can solve the problem using the Nuget Package MSBuild.Microsoft.VisualStudio.Web.targets
so the build process does not require any change to the build server.
Install-Package MSBuild.Microsoft.VisualStudio.Web.targets
Details:
remove the element for "ServiceModels.targets" in the .csproj file
remove the target WebApplication from the build command (in yaml)
Ran into this same issue. Did the following to resolve:
Installed the Microsoft Web Platform Installer
Copied Directory "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\WCF" from dev laptop with Visual Studio 2012 to the build server
I've had the same error - my issue was that MS has modified the way MSBuild looks for the versions of VS in the build process template.
Make sure to use the right build process template.
If using TFS2013 and VS2013 use TfvcTemplate.12.xaml
I ran into this same error. In my case, the problem was that my Visual Studio 2008 project didn't get upgraded correctly, probably due to files being marked "read-only" by my source control. To fix it, I loaded the solution in Visual Studio 2015 with everything checked out.
The specific line in the .csproj file changed from
<Import Project="$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\WCF\Microsoft.VisualStudio.ServiceModel.targets" />
To
<Import Project="$(WcfServiceModelTargetPath)\Microsoft.VisualStudio.ServiceModel.targets" />
If you are using VS 2022 build tools, it is no longer in the individual components section. It is on the first tab "Workloads", included in ".NET desktop build tools", you will see it in the list on the right-hand side when you select it.
I have a solution which can be deployed for SharePoint 2007 and SharePoint 2010. There are common files like .css files and images. When I am deploying solution for SP2010 I use mapped folder (_Layouts). And this folder have to copy my files to the server. The point is that I don't want to copy the same files to this folder. And I add them as a link. But Visual Studio does not want to copy files to destination folder.
If I understand you correctly, you want to deploy linked files. This is not just a SharePoint limitation, but a Visual Studio limitation with web projects. I believe the same limitation exists for SharePoint projects. Please refer to the following link:
https://connect.microsoft.com/VisualStudio/feedback/details/665257/
I've resolved this issue. Just removed the links and added real files.