I created a new SQL Server Database Project in VS2013 (Update 3) and attempted to build but it fails. The only build output I receive follows:
------ Build started: Project: Database1, Configuration: Debug Any CPU ------
Creating a model to represent the project...
Done building project "Database1.sqlproj" -- FAILED.
Build FAILED.
========== Build: 0 succeeded or up-to-date, 1 failed, 0 skipped ==========
If I build the project via MSBuild.exe with detail verbosity I see the following inner failure:
Task "SqlBuildTask"
Creating a model to represent the project...
Done executing task "SqlBuildTask" -- FAILED.
After searching the web I have tried the following to resolve this to no avail:
-Restart VS
-Restart machine
-Repair VS Update 3 and reboot
-Repair VS2013 and reboot
What am I missing?
After contacting a friend at Microsoft, he suggested repairing the Data Tools install at
https://learn.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt
And that resolved it.
Thanks Chuck!
I had a similar issue and as mentioned in the accepted answer repairing is the solution. But unfortunately the link did not gave me an exe that says repair/UnInstall. I went ahead and run exe still issue persists.
I resolved it by updating the sql data tools using Extensions and Updates. Following are the steps.
Open visual studio.
Go to tools menu and click on Extensions and Updates.
Under the updates you will find an update for database proj.
By clicking it, it will download an exe.
When you run the exe it will ask for Repair/UnInstall.
Click repair and proceed.
Also check that you are using the correct version of MSBuild. There are usually multiple MSbuild exe's on your machine. The 14.0 version should be working with the Visual Studio 2015.
I had this issue as well, but the problem was with the value in the project property "DSP". I had edited the proj file to build a dacpac for SQL 2012 and then edited it again for SQL 2014, and was getting this error for both.
The original project that was targeting SQL 2008 worked fine still, so it wasnt an installation issue.
In my editing had misspelled the values for the DSP element.
<DSP>Microsoft.Data.Tools.Schema.Sql.Sq110DatabaseSchemaProvider</DSP>
And it should have been (where sql is spelled with the L)
<DSP>Microsoft.Data.Tools.Schema.Sql.Sql110DatabaseSchemaProvider</DSP>
Fixing that spelling resolved the error.
Related
I'm using the built-in Visual Studio test tools (Test -> Run -> etc in the menu). I just started having a problem where I get the following error when I try to run tests
[3/29/2018 1:39:14 PM Error] System.IO.FileNotFoundException: C:\Users\brubin\AppData\Local\Temp\VisualStudioTestExplorerExtensions\MSTest.TestAdapter.1.1.18/build/_common/Microsoft.VisualStudio.TestPlatform.MSTest.TestAdapter.dll
at Microsoft.VisualStudio.TestWindow.Controller.TestPlatformProvider.PerformShadowCopy(IEnumerable'1 testExtensions)
That's followed by some errors that say
Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again.
When I look at the folder C:\Users\brubin\AppData\Local\Temp\VisualStudioTestExplorerExtensions\MSTest.TestAdapter.1.1.18/build/_common/, there are no files in that folder. However, I haven't knowingly changed anything about my test setup and this was working several days ago, so I don't know why it would have stopped working.
My projects are using the MSTest.TestFramework (MSTest V2) version v1.2 NuGet package.
One thing I noticed that may have caused this problem is that if I go to Tools -> Extensions and Updates, I see that my Microsoft Visual Studio Test Platform was updated a few days ago, on 3/23 (I think that's when I installed a Visual Studio update). However, if that broke something, I have no idea where to look to see what's broken, or how to fix it.
For me, clearing the VisualStudioTestExplorerExtensions folder and restarting Visual Studio (as per this github issue) did the trick. In my case, it contained two folders for different versions of MSTest.TestAdapter, I don't know whether or not that's relevant.
For anyone else who stumbles on this question, the problem was caused because a few of my test projects didn't have the MSTest.TestAdapter NuGet package included. I added the MSTest.TestAdapter package to all of my test projects, and the problem seems to be solved permanently now.
I spent the whole last week trying to solve the same issue. Only yesterday did I realize that running tests from the console is a time saver. Much to my surprise, I've just moved all my project -which was inside a "OneDrive" folder, to a different location. Now, it works like a charm! All my tests run from the Visual Studio IDE. I don't know if moving the files had anything to do with it, but you can give it a try.
Reinstalling all solution's Nuget packages fixed this issue for me.
Please run this command on the package console:
Update-Package -reinstall
then try again, or restart VS, then try again.
Reference: https://ardalis.com/force-nuget-to-reinstall-packages-without-updating/
Its a bug in Visual Studio. Upgrade the Visual Studio to version 15.7.
https://developercommunity.visualstudio.com/content/problem/222892/filenotfoundexception-microsoftvisualstudiotestpla.html
Yes you need to update "MsTest.TestAdapter" on all testprojects. The easiest way is to rightclick on master solution and click on manage nuget-packages. Then select " installed " tab and see if there is installed TestAdapter on each testprojects. If necessary you can update TestAdapter to newest version. Then restart Visual Studio and it should work.
I am unable to build any xamarin project in Visual Studio 2017 mac.
It gives me the following error:
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/iOS/Xamarin.iOS.Common.targets(81,81):
Error MSB4057: The target "_DetectSigningIdentity" does not exist in the project. (MSB4057)
It was working fine before, i dont remember updating anything on my visual studio.
It is not specific to solution. None of my project gets build.
Any suggestions please??
I have solved the problem on my own installation.
open update menu
select alpha channel
download and install all
restart
hope this helps
We are in the process of upgrading our TFS 2013 server to TFS 2015. In that regard I have run into an issue when trying to perform an application build on a build agent with the new version, using our XAML template build script (which was created in TFS 2013).
Most of our solutions use the above-mentioned template when we build them. The solutions (sadly, still) use setup projects (.vdproj) to generate an MSI package for the application. To build the setup project, and produce an MSI, for a given application; we call the devenv.exe (in our case, it points to Visual Studio 2013) in our template build script:
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\devenv.exe /Build "Release|Any CPU" "d:\<path_to_solution>\solution.sln" /Out c:\temp\out.log
However, on our new build agent no MSI is produced, and calling devenv.exe yields neither any output, nor any error messages. If I try to call devenv.com, however, it starts building, but still no MSI is being produced.
When things start to build using devenv.com It seems like it is completely disregarding the setup project (I have checked the build configurations, and the setup project is checked for build on the "Release|Any CPU" configuration).
I have looked at build logs, build process activity logs, and I have also tried to perform the steps manually on the build agent, but I haven't been able to find anything that could point me in the direction as to what might be causing the issue.
Does anyone have an idea what could be the reason for this? Could it be an issue with TFS Build 2015? The only difference between the old setup, and the new - as far as I can tell - is the following:
VS 2013 was installed on C: rather than D: on the new build agent, i.e. the path to devenv would be different, but that should not matter as long as the build script is looking in the right place, and finds it...
We use a different drop location than what we used for the old setup
Appreciate any help and suggestions I can get.
Problem solved, and everything is now building successfully. I did not do a good enough job of looking at the diff between the setup we had on the build agent we used for TFS Build 2013 vs. the one we set up for TFS Build 2015.
Firstly, to be able to build setup projects in VS 2013, one needs to install the Visual Studio 2013 Installer Projects extension on the build agent.
However, there are some bugs with this extension that often causes building setup projects to yield the following error message: "An error occurred while validating. HRESULT = '8000000A'". This error can be fixed by modifying the registry, as described in this SO post.
Building the setup projects using devenv.exe, however, still doesn't work. I have not been able to figure out why, yet.
Use the Vnext build in TFS 2015 to build .vdproj. You just need to add one additional build step i.e "command line" then call devenv.com to build.
Such that,
tool :
C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.com
arguments :
HelloWorldTestInstaller\HelloWorldTestInstaller.vdproj /build release
This will help you.
After building my application I get in the test output:
------ Discover test started ------
Exception has been thrown by the target of an invocation.
========== Discover test finished: 1 found (0:00:01,457) ==========
I'm using Visual Studio 2012 Professional on win7 32bit.
Tried:
repairing vs2012
reinstalling vs2012
changing configurations
changing path to
Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll
Nothing worked...
Any ideas?
Previously I worked with Visual Studio 2010 Express edition.
Application is correct - I made just simple class library and test project just to be sure it works. And it doesn't. The same project works with my student premium version.
Ok
I looked again in http://connect.microsoft.com/visualstudio and tried also:
moving project files to another location than default
changing security rights in files and folders properties
run vs as administrator
Nothing really worked until i found by chance vs2012 update 1
(under the "Additional Software" category)
After download and installation everything works fine.
In my case, right clicking and selecting "Debug Tests" on a test method would not do anything. It was an existing test project. The issue was that the test project was not even included in the solution's build list. Somebody took it out from the solutions build list. Anytime I would select "Debug Tests", the projects were built but nothing happened.
Confirm that the test project is going to be built with the solution by right clicking on solution in the solution explorer, and then configuration manager. Ensure that the test project is checked-on for build. Those minor things that cause big problems!
When I try to publish in Windows 7 from Visual Studio 2010 via File System, no files are added to my target folder. If I choose "Replace matching files with local copies", nothing happens. If I choose "Delete existing files prior to publish", it deletes the files in the target folder, but no new files are published. This is the output I get:
Deleting existing files...
Publishing folder /...
========== Build: 3 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Publish: 1 succeeded, 0 failed, 0 skipped ==========
Any thoughts?
EDIT: Forgot to mention that I'm running VS as an Administrator. If I don't, publish will explicitly fail.
I ran into the same problem, after checking publish output, event logs, turning on and checking visual studio logs etc I then decided to remove the web publish (via add/remove) which I believe had been recently updated to v1.0.30810.0. This resolved the problem.
I hope this issue has been resolved in the meanwhile, but something similar happened to me recently. In my case, the Build Action of the file had somehow been set to None. If the Build Action of a file is set to None, Publish Web will skip the file. To check the Build Action, select the file in the Solution Explorer and press F4 to go to the Properties Window.
I had the same problem just after installing the latest windows azure SDK.
The solution was to match the build configuration with the publish configuration.
In my case i was building for "Debug - Mixed platforms" and publishing for "Debug - Any CPU"
Credit goes to the following:
http://geekswithblogs.net/ToStringTheory/archive/2012/06/11/lsquopublishhelliprsquo-resulting-in-directory-with-no-files.aspx
This happened to me too. To solve this:
Open the control panel, click the programs icon and remove web publish
In VS2010 click the tools drop down menu and select Install Web Components
I am not sure why this happened but I suspect that the VS2012 installation could have upgraded the web deploy component when I was working with Azure Web Sites in VS2012.
UPDATE: This stopped working the next day! Now I am publishing the application through VS2012.