In Visual Studio 2013, is there a way to ignore column ordering when doing a Schema Compare? I see that this feature was removed from Visual Studio 2012 (according to this: https://stackoverflow.com/a/13848952/188740), but I'm hoping it was brought back in version 2013.
Here's a quick visual to illustrate what I'd like to ignore:
As described on this blog post, Ignore column order is now an option in SSDT version 17.0, which is compatible with Visual Studio 2015.
If you’ve ever had to deal with accidental data
motion when putting a column in the middle of a table definition,
you’ll know how hard this can be to spot and manage. In this release
you can now check the “Ignore Column Order” option in the Advanced
Publish Options. This will append new columns to the end of an
existing table rather than altering the table structure to add the
column in its listed position.
You can find the setting by going into the Advanced... button section of your publish profile, as well as in the Advanced... button section of the database project properties' Debug tab.
You can also achieve the same effect by adding the following element to your publish.xml file:
<IgnoreColumnOrder>True</IgnoreColumnOrder>
Unfortunately I do not know of a way to have this work in Visual Studio 2013, but hopefully you have upgraded to a newer version of Visual Studio by now :)
Ignore column order is now available in VS2015.
Additionally, for relational and Azure SQL databases SSDT 17.0 GA includes a highly requested improvement to ignore column order in upgrade plans as well as numerous other bug fixes.
See: https://blogs.msdn.microsoft.com/ssdt/2017/04/19/announcing-the-general-availability-ga-release-of-ssdt-17-0-april-2017/
The 'Ignore column order' setting is not available in visual studio 2013. There are Tentive to reintroduce this option in the future.
Sources: Microsoft
This feature is also available in Azure Data studio -> Schema Compare -> Ignore Column Order.
Related
I'am staring using Oracle Developer Tools for Visual Studio Code but miss something versus what i did in past with sql server tools:
Let's say i have a table whit this name
T_PREFIX_TABLENAME
I'am used to type part of TABLENAME and find it: simply typiyng "TABL" make intellisense working and finding corrispondent result with a like operation, with ODT this does not work and i have to type the initial part of the table name to find it, let's say "T_PREFIX_TABL" to find same results
Since all table have a long common prefix (databas is not mine so cannot change this) i have to write large part of text making intellisense quite unuseful.
I try even Oracle Developer Tools for Visual Studio 2019 with visual studio 2019 professional but in this case intellisense simple does nothing.
I try other way: drag & drop table or comlumn from server explorer to query windows but in visual studio 2019 an entire select query in created while in vs code nothing appens.
Is there a way to have intellisense smart like the sql server tools one's?
Thanks
I believe this issue with autocomplete incorrectly doing a "begins with" search, was a bug introduced in Oracle Developer Tools for VS Code version 19.3.3. It has since been fixed in 19.3.4.
In Visual Studio 2015 is it possible to get a timestamp included for each line when a file is updated? So for instance:
2016-06-28 10:30:45.106 Replacing....
The Visual Studio Productivity Power Tools has an option to do this (VS2013 version, VS2015 version) called "Timestamp margin".
From their site:
It also has many, many other features. You can turn each feature off separately though, so if you don't want the other features you can turn them all off.
I haven't needed to edit reports in several months, so I'm not sure specifically when the below behavior changed. I'm on Visual Studio 2015 Update 1 Professional with the latest version of SSDT as of this post (April 2016, 14.0.60413.0). The situation is the same in Visual Studio 2013 Update 5.
I have a database with a ton of information in it for various products. I'm trying to use SSDT (report designer) in VS to filter down to only retrieve a single result for a report on a given product in the table, but this doesn't appear to be possible.
In previous versions of SSDT in Visual Studio, I was able to right-click a dataset and edit the query manually. I would SELECT the columns I wanted, then I could add my own WHERE clause to filter by a report parameter. I cannot do this anymore--the options no longer exist. I can edit the query manually, but only at the level of the data source. That isn't helpful because the data source has no concept of a parameter to filter by, only the report does. This MSDN article is incorrect here, see the screenshot below.
What is the correct way to retrieve only a single result for (or filter in general) a given dataset in SSDT/Visual Studio report designer?
Dataset properties (field names redacted):
There are only two ways in which to retrieve only a single result.
Within SQL Server restrict your data using a WHERE clause or similar concept (INNER JOIN etc etc)
within SSRS restrict your data using a parameter
These are the only methods.
For a couple of weeks now I have been unable to merge Views within Visual Studio 2013 in response to conflicts when getting Source Code from Visual Studio Team Services. I am sure I used to be able to this (we recently moved from Visual Studio Professional 2012 so I cannot be one hundred percent certain - automerging may have been sufficient in the early days of the project).
The "Accept Merge" and move to next change/conflict buttons are all greyed out and inoperable. See screenshot snippet-
This originally only happened with Views, but now seems to affect some other classes. Changes are highlighted and indicated on the scroll bar so the diff tool otherwise appears to be functioning. This only originally affected me, but now affects a new colleague into the team.
I can still either Keep Local Version or Take Server Version but this is rarely sufficient. This leaves me manually altering the local copy to apply changes highlighted by the merge tool. (Edit - See a better workaround in "Second Update" below).
Has anyone come across this before?
Visual Studio 2013 Premium (patch RTM/Update 1/Update 2 - all with the same problem), with Resharper 8.2 (originally 8.0.2) C# and Web Essentials installed. Running on Windows 7 Professional x64.
Project is ASP.NET 4.5 using MVC 5.1.2 (now additionally updated from MVC 5 where the problem first occurred) (upgraded from MVC 4 following the upgrade instructions on the ASP.NET website) in C#, using latest versions of Razor (3.1.2) and Entity Framework (6.1.0 RTM).
Edit: Initially a repair install of Visual Studio 2013 appeared to have fixed the issue. It has now however returned exactly as it was before. Since it took an hour to do the repair I cannot repeatedly do this in order to merge views. I am currently able to round trip the solution between Visual Studio 2012 Update 4 and Visual Studio 2013 in order to do merges in Visual Studio 2012 where it is working normally.
Second Edit: I am currently manually resolving conflicts by selecting the desired code (local/server), saving the merge window and then closing it which will prompt to accept the merge result. This seems to function but is obviously sub-optimal. It may however be helpful for other users.
In the event, installing Resharper 8.1 on top of 8.02 appears to have fixed it fixed it briefly before the problem returned yet again. I had previously completed a repair install of Visual Studio Premium 2013 as well - which briefly seemed to have fixed it before it broke again. I only mention it in case the fix is cumulative.
I am unclear if it was a bug in Resharper that was somehow preventing the merge, or a persistent problem with the installation that the upgrade cleaned up (Resharper removes previous versions and then installs updates, rather than attempting to install over the top). Update - I am extremely confident that this is not related to ReSharper and that it was the configuration of Visual Studio as a result of re-installing the extension and not the extension itself that fixed the issue.
In either case, the issue (for now) seems to have disappeared and this seems to be related to the upgrade, or is an extremely strong co-incidence.
Colleagues with the same versions of Visual Studio and Resharper, working on the same project, the same version of Windows and (in one case) the same hardware were not affected, so it seems likely it is an edge case niche issue caused by corrupted data somewhere.
I have a current working theory that this is related to different patch versions of Visual Studio (for example Visual Studio 2012 Update 2, Visual Studio 2013 RTM, Visual Studio 2013 Update 1, Visual Studio 2013 Update 2. This only affects Visual Studio 2013 for us.
Simple solution I use is carry on with your manual merge process once you are done simply Close the Merge-* tab (the one you are using to merge files) this will bring up a prompt for confirming if you want to Save the changes made (this is the merge changes you made to your local file) click 'yes' Now it comes back to Resolve Conflicts tab and brings up another prompt asking if you want to Accept Merge Result, click 'yes'(this is same as the button Accept Merge)
Since you have VS2012 installed and merge is working there, you can create a link to its TF.exe in VS2013, similar to one on the picture below, and fix the issues there. Set Command to c:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\TF.exe and Arguments to resolve.
You do that in Tools->External Tools.
I have some issues with my reports since I have updated them to VS2010 format.
Even though I have modified references to from v9 to 10 for Microsoft.ReportViwer.Common and Microsoft.ReportViewer.WinForms as well, when I try to type code. in a field, what is after "Code." is always underlined with red and I get #ERROR instead of the value I want when I print the report. I know it is case sensitive and I double checked the spelling multiple times.
Moreover, I don't know why but I have errors with the Fields! syntax; I seem to have to use the Fields().value to get them to work (at the places I don't need to call custom code too)
These reports worked well before conversion (over 20 reports converted this way) but do not now. Seems like custom functions are not "seen" by the report designer. I tryed to make them public, shared; all I had is the same stupid #ERROR display.
I want them to work in VS2010 to avoid always having to modify them in VS2008 and then go back in VS2010
It's a winform application with framework 3.5
Any idea of what could cause that and what is the remedy?
Many thanks
Nico
There are a couple of ways to use custom code in SSRS. Firstly you can enter VB directly into the window under
Report -- >Report Properties --> Code
Another way is to write a custom DLL (which can be done in any .NET language of course), which then needs to be copied to both your dev machine and the production report server.
You then need to create references to that assembly in the project using:
Report --> Report Properties --> References (I assume you know this).
If you are not using your own custom assembly, and just using a reference to one on your machine then there could be some confusion on the server as to where to find the dll's. You may need to copy DLL's to the folder as indicated in the KB link below:
http://support.microsoft.com/kb/920769
When you drag a field onto a tablix or textbox, and have a look at the value expression, does it use the Fields!Fieldname.Value syntax? That syntax is natural to SSRS so it sounds like something seriously broken in your visual studio 2010 there if that is not working. I take it you installed visual studio 2010 to create web applications. What you haven't explained is which version of BIDS or SSDT you are using. If you are developing reports for SSRS 2008 R2 or earlier, then these are not compatible with visual studio 2010. There's no compromise there.
If you are developing for SSRS 2012, then you are using either SSDT by itself (which installs a shell version of visual studio 2010) OR if you already have visual studio 2010 then you need to install service pack 1 for VS2010 and then install SSDT from the SQL Server 2012 disc.
http://msdn.microsoft.com/en-us/library/hh500335(v=vs.103).aspx