Options
I don't want it to recognise my SqlProj file (10.3+)
ivanjh
Posts: 12
We have a ".sqlproj" file that includes all the scripts generated by the "Create Scripts Folder..." option.
Because the scripts aren't compatible with a Visual Studio database project, the build action is set to none. This results in a <None> element instead of <Build> in the sqlproj file.
Since upgrading to 10.3, we can't compare against the folder containing the scripts, since the existence of the sqlproj file overrides the set of files to compare with... and our sqlproj file has those scripts all set to None - so it basically considers the scripts folder empty!
Is there some way to tell SQL Compare to ignore the sqlproj file?
Or some way to get it to include the "None" action items?
Or is switching all my scripts to "Build" and setting the project to not build at the solution level the only answer?
Because the scripts aren't compatible with a Visual Studio database project, the build action is set to none. This results in a <None> element instead of <Build> in the sqlproj file.
Since upgrading to 10.3, we can't compare against the folder containing the scripts, since the existence of the sqlproj file overrides the set of files to compare with... and our sqlproj file has those scripts all set to None - so it basically considers the scripts folder empty!
Is there some way to tell SQL Compare to ignore the sqlproj file?
Or some way to get it to include the "None" action items?
Or is switching all my scripts to "Build" and setting the project to not build at the solution level the only answer?
Comments
I am little confused by your post.
".sqlproj" files are for SSDT projects. SQL Compare (and SQL Source Control) now recognise SSDT project files.
Are you able to move the ".sqlproj" file to another folder, I believe that can be located anywhere.
Many Thanks
Eddie
Senior Product Support Engineer
Redgate Software Ltd
Email: support@red-gate.com