I have Visual studio 2019 database Project which has gone out of sync, because of direct updates on the DB.
How do I refresh my visual Studio 2019 Database Project from Source Database ? Did not any option to Refresh/Regenerate.
There's a "Schema Compare" command under the Tools Menu -> "SQL Server" -> "New Schema Comparison". Use that to compare your live database (source) against your project. I'd suggest that you use the options to ignore things that don't matter to you. I'll typically ignore users, permissions, comments, whitespace, and such, but you do get a little choice of what to pull over from the results. Just be careful that what you pull over doesn't overwrite changes you want to keep. You may have to do some manual editing for those cases.
Related
I will start by saying that I am not a developer, I use Visual Studio only for TFS as a means of contributing to Work Items in our project (I am a product owner).
On TFS web, there are some fields we have that give us a multiple-choice made up of a number of checkboxes. In the Team Explorer / Work Item view in TFS, these fields do not work and give me the following error:
Could not find a part of the path 'C:\ProgramData\Microsoft\Team
Foundation\Work Item Tracking\Custom
Controls\16.0\GLMultiValueControl.wicc'.
I assume what is happening is that this file defines the allowed values for this field, however the file isn't there. In addition, the following directory doesn't exist either:
C:\ProgramData\Microsoft\Team Foundation
Is there some command I need to run to synchronise my local copy of TFS with the server? I find it surprising that the Team Foundation folder doesn't exist, maybe I've missed something with the installation?
I installed Visual Studio 2015 Enterprise RTM and only seeing "references" from Code Lens. We are using TFS for source control. I expect to see related commits from TFS. Based on this article, I have everything enabled in options:
Here is what I see in VS:
Is there anything wrong with my VS setup?
The TFVC lenses that are part of CodeLens only work when connected to a version of Team Foundation Server that is running the background job that generates the historical data. This means that you need to be running at least TFS 2013 or 2015 in order for this feature to work. Some features require a specific version of Visual Studio.
It is also possible that your server admin has disabled indexing on the server, one can do that using the tfsconfig codeindex command on the application tier.
I have been searching the web for a clean solution on how to migrate our 2010 tfs collections to our new tfs 2012 server, but no luck. May someone please assist with the steps or a good blog I could look at to achieve this process. The reason we want to do a MIGRATION and not an upgrade is because we got new hardware and would first like to trial TFS 2012 before we upgrade our live environment. Therefore we would like to import all our collection including the work items and build process templates.
Here is a decent blog post: http://mohamedradwan.wordpress.com/2013/01/05/upgrade-tfs-2010-to-tfs-2012-with-migration-to-a-new-hardware-series/
The basic steps you want to follow are:
Backup all of your 2010 databases.
Restore those databases on the SQL Server on your new hardware.
On your new hardware, install TFS 2012
When it comes time to configure. Select the upgrade option.
It will asks where your databases are. Select the SQL Server that you used in #2.
Press Go.
Note, if you want to test 2012 with the same clients you are using for 2010 then you'll need to "clone" the system otherwise your clients will get confused. To do that, see http://msdn.microsoft.com/en-us/library/vstudio/ee349259.aspx
You can move a collection at a time using the detach option in 2010 and attach it back to 2012 using the attach option there.
See http://msdn.microsoft.com/en-us/library/dd936138(v=vs.100).aspx
I am trying to work with Visual Source Safe while developing an ASP.NET MVC 3 site in Visual Studio Web Developer Express. There doesn't seem to be any integration between VS and VSS so I have to check in and check out manually.
During the course of a day, I create and modify many files, and so it is annoying to have to do VSS checkin/ checkout every time. Is there anyway to, instead, just check in the entire site at the end of the day?
That way, I will have a working copy of [Monday's] version of the site, and on Tuesday at the end of the day I would have a working version of Tuesday's version of the site. Then, can these be deleted over time?
The express edition of Visual Studio doesn't provide any integration with VSS. If you'd like to do the check-in/check-out directly in Visual Studio, I recommend you upgrade your VS.
Also, you can take advantage of the VSS command line. You can execute the command to check in the entire site at the end of the day, and perform check-out on the next day.
http://msdn.microsoft.com/en-us/library/asxkfzy4(v=vs.80).aspx
Although the command line may simplify the process, I still recommend you check in the modifications in time.
Does a feature like "TFS auto-checkout before checkin" exist, so that I don't checkout any file until the moment I say "checkin", e.g. in case I only change files temporarily - which happens all the time.
In other words, client-side I want to work as if using subversion, regardless of what the TFS server might think. This must be possible, I just wonder if it is easy to setup.
In yet other words, until and unless I say 'checkin', other users shouldn't (be able to) bother what files I'm editing.
These answers are fine assuming you always work in Visual Studio. But imagine the scenario of editing a bunch of files outside of Visual Studio and you want to use Windows Explorer TFS powertools to automatically checkout files which were just modified. Well, there is no automatic checkout. What I ended up doing was to sort the files by the "Date Modified" column and then individual selecting the modified files only. You can't select any files which might be added, as the TFS power tool Windows extension will grey out the "Check Out for Edit.." The other frustration is that TFS power tools doesn't have a file icon to differentiate if a file is currently checkout or simply not yet added to TFS. Basically, TFS is terrible working with more than file at a time unless you are exclusively working within VS, but who does that.
SVN kicks TFS when it comes to this type of scenario.
You can tell Visual studio not to check out on edit, go to tools, options, source control, environment. Then select the behaviour you want. If you choose editing to "do nothing" and saving to "prompt for checkout" it should be pretty close to what you want.
You could also look at svnBridge which allows you to use TortoiseSVN with TFS. I assume that the point of svnBridge is to allow developers used to SVN to use TFS without having to change the way they work, so it should meet your needs.
A combination of both of these should get you close.
From time to time I hear from people who dislike the automatic check out behaviour common with TFS. One of the great things about TFS is the the pending changes list that shows you the files you have currently checked out and allows you to easily undo any un-intentional check outs. While I personally find the auto-checkout features a productivity boon - like most things there is a preference that you can use to adjust the default behaviour if you find it causes problems with the way you like to work.
In Visual Studio 2008 (with the Team Explorer 2008 installed), go to Tools, Options, Source Control, Environment and change the Checked-in items for Saving and Editing to "Prompt for check out" rather than the default which is "Check out automatically".
No. When you check in TFS will checkin those files, you have to just undo those files.
However checking out a file doesn't stop others from checking them out, unless you've locked them. This non exclusive locking is the default behaviour.
No. But you can do one thing - Open solution in 2 Visual Studio, One in which solution is Online and another in which solution is offline. Do all your changes/work on Offline solution. After completing your task.
Go to first VS (Online) and checkout the files containing your changes.
Go to Second VS (Offline, containing your changes) - It will prompt for file changes and click "No to All" so that all your changes persist.
Press Save All.
First Solution (Online) will prompt for new changes and click "Yes To All" so that all your changes done in offline mode will get in new files.
Get Latest. - Any conflicting changes will be reflected (Try automerge - if you're lucky will work perfectly)
CHECK-IN
Though a tedious task but a workout for your question.