Problems building an Sql Server Database Project: comparison, refactoring warnings, etc - sql

A colleague of mine is having problems building a Sql Server Database Project in visual-studio-2013. He shared his screen with me, hoping I could help him solve the following issues:
In case you can't see the image, there's a build error stating that "The comparison cannot continue until the build error is resolved" and a build warning that goes "Refactoring operations exist in the source, but will not be shown in the comparison.".
Not being too familiar with Sql Server DB projects, I tried searching the exact same messages on Google... only to find absolutely nothing.
Can anyone help? What does these messages means, why are they appearing and how can we expect to successfully build the project?


I had this same issue but it went away when I followed the instructions of the accepted answer of this post: VS2013 Database Project fails to build.
It turns out that the project was not building. The error described in this post was misleading and was probably only a symptom of the real error which was that the project could no build.
In case that link is no longer available, the solution was to install the Microsoft SQL Server Data Tools. You can do that by downloading the install package from here.

Related

Failed to install SQL Server 2019 Express

I wanted to learn SQL to create my own database to serve for my future project but things seem not to be smooth as expected from the first step. I struggled with installing the SQL Server for days with different times of uninstalling and reinstalling. The installation Progress has just constantly thrown me warning window with the content was:
The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.
I believed that the old SQL Server was completely uninstalled by deleting anything related thing include files in Program Files, Program Files(x86), and its registry.
I searched and followed many threads with the same issue on some forums but still got no result.
After skipping that warning by canceling it, the installation completed with failure shown in the picture below. Your help would be much appreciated.

SQL Server Integration Services Package

I have just recently started using SSIS and it's been a great ride so far. I get an error message when attempting to add an existing package. My guess is that packages that were created on an original computer cannot be globally accessed even if you have the .dtsx file?
Below, is a link of the image of the error I am getting.
http://imgur.com/B95pVg5
Please give me any help!

Fail build on static code analysis warnings with msbuild and bamboo

Using bamboo v5.7 with msbuild v12, how do I fail a build if there are any static code analysis warnings? We do have our projects all set to treat all warnings as errors so the project itself doesn't build, but bamboo is not detecting this and continues on.
This seems basic, what might I be doing wrong?

The simple answer is you are doing nothing wrong, nor are you missing anything.
While it seems like basic functionality, Bamboo's MSBuild task currently doesn't support reading, reporting or failing the build on Warnings or Errors. The task only fails because MSBuild (or XBuild if you are using Mono) returns with an error code when a compiler error occurs.
Also, MSBuild doesn't actually support failing on all warnings either, as you can see here.
You have a couple options.
You can use one of the options in the referenced post
You could roll your own MSBuild log parser plugin using Atlassian's Plugin SDK.
You could make a simple script that is executed after the build, reads the logs and returns a non-zero integer if there were compiler warnings.
You can vote for the issue in the Atlassian Jira and also for the related issue for parsing build details.
Whatever your solution, I hope you share it with the many of us that have run into the same problem. It seems to be something quite common, so I was surprised there wasn't an issue already open for this in Atlassian's Jira instance

For VS 2008 and later, a new project setting was added for this. See this link.

Failure installing SQL Server 2008 R2 Express X64

I am having a serious problem installing this (from web platform installer and from the downloaded installer). I have a laptop with win7 x64 enterprise on it.
I have read the forums and tried all the solutions I have found, from permissions, .NET framework to copying the setup files etc. These did help move the install on but in the end it always fails for the database. I have tried following MS advice on trying to read the log files to see where it fails which is why I looked at some of the solutions but the fixes didn't work. What makes it worse is the solutions for retrying the install (removal of things from the registry) has made things worse on the laptop as other stings stop working every time I remove the SQL keys.
I was hoping someone here could look over the logs to see if they could give me a better indication of whats wrong. Problem is I can't see a way of attaching a zip file here

Compile error in VS.NET 2008 (VB.NET) that I can't get rid of!

I can't shake this error when compiling my Visual Studio.NET 2008 solution. The project that's generating the error is a VB.NET Web Application in a 12 project solution (mixed types and languages).
I've tried all the tricks I can find on google, and the obvious of removing the directoy and folder manually.
I'm running Vista Business 32 with VS.NET 2008 SP1. This just started happening out of the blue today and I've rebooted a bunch and even re-applied SP1 for VS.NET.
Any ideas or has anybody seen this?
vbc : error BC31019: Unable to write to output file 'G:\Projects\TCA.NET\TcaNet\WebUI\obj\Debug\TcaNet.WebUI.pdb': Unspecified error
Update:
After thinking about this and not finding any solutions from answers or via the Internet, I went ahead and moved my entire solution to my C:\ drive vs. my G:\ drive (both are local). Doing this fixed my compile problem for some reason.

I had the same error a few weeks ago when I was compiling on my server from my laptop. Turns out that if G: is a network drive, this could fail. Microsoft have said that fixing this is not a priority, and that there's much better ways of doing things (such as source control). For a one-man project though, it's a pain.

Restart IIS on local.
If that's not the issue then, install Unlocker and try to delete that pdb file when you get the error, Unlocker will tell you which process is holding an open handle to that file.

I have found a list of thing to try to fix your problem :
Zen-turkey Fix list
Hope this help!

maybe it is a dependency problem. check the build order of all the projects..
sysinternals tools should be of help here. using process explorer, are you able to find out if any process is locking this file? another useful tool is process monitor. after applying a filter for the pdb file, capture a trace of all file access activity..

It's probably bug in VB.NET compiler. The error message is incorrect, the real problem is missing file referenced from the project file. For example .vb file.
In my case, I found the missing file and added it, then devenv compiled fine again.
Someone reported that to MS here

Although it is very old thread, but I got this error today and the following link solved it. Hope it help someone reading this.
VB.NET .pdb fix

After thinking about this and not finding any solutions from answers or via the Internet, I went ahead and moved my entire solution to my C:\ drive vs. my G:\ drive (both are local). Doing this fixed my compile problem for some reason.

I had this in Visual Studio 2005 except it was Error 1. I restarted my machine and it fixed the problem.