just upgraded a VS2010 project to VS2013. Project was already under source control in TFS.
Now everytime i open the solution, i receive a box that states something like "Project is already under source control but is not currently configured to use integrated source control. Would you like to configure now? Yes or no"
So if i click on 'Yes' it brings up the 'Change source Control' which shows it not connected to any server or anything. I am unable to click on the 'Connect' checkboxes and if I click 'bind' it will throw an 'unspecified error'
Help please. I need to ensure i can check in/out changes so that other developers are able to get the latest.
After investigate a few about your problem, i think you have two options:
Make a new repository with your project using vs2013.
Use your project (that is on TFS) with vs2010.
Related
I thought this was a simple question, and still nothing works.
My first use-case is that the IDEA 15 (Community) appears to NOT have a repository configured. The *Plugins" tab in the Settings window / dialogue supports three operation aside from clicking on a plugin.:
A button for [Install JetBrains plugins] ... This seems to be things downloaded with the installer or updates;
A [Browse repositories plugins] button ... which contains an "empty" list Further this dialogue contains two buttons for:
A [Manage repositories]
[HTTP proxy settings] - Proxy configuration / setup
An [Install plugins from disk] button ... which does what it says ;-)
This question to ask is, what URL do I need to put into that:
* The [Manage repositories]
... list because the clean install had "nada" in that list.
The list of JetBrains plugins isn't the same as the list on the plugins repository web page:
https://plugins.jetbrains.com/
In fact IDEA help pages recommend using the JetBrains repository... They do not seem to want to let one know the URL.
Also, what is the "Community" plugins URL? At the very least I'd like to verify that/IF the JetBrains plugin-list is updating (as there's no "update list" option to be seen).
Weird huh?
I had the same problem while using the Community edition and trying to install the lombok plugin. Setting the HTTP Proxy to "Auto-detect proxy settings" resolved it for me.
It's under browse repositories -> HTTP Proxy Settings -> HTTP Proxy -> Auto detect proxy settings.
The [Manage repositories] list should be empty, unless you have some private plugins repository.
A [Browse repositories plugins] button should show you all the plugins, if not then check your firewall or proxy settings, or click on the Reload button.
[
I don't know the specific URL, either, but Meo's answer is correct in saying that there's no need to add it manually. It sounds like you're confused by the difference between the list you see on the site and the list you see in IDEA CE.
The reason for the difference isn't a missing URL at all, but rather that many of the plugins listed on the site are not enabled for the Community Edition, so it doesn't display them. The PHP plugin at https://plugins.jetbrains.com/plugin/6610 is an example. While that page doesn't make it clear that it requires the Ultimate Edition, you can find out by scrolling down to the Updates list and clicking the (latest) version number. There you'll find a Supported Products list, where the Community Edition is listed as being incompatible because the plugin requires the "ultimate" module (a module that is only included in IDEA Ultimate Edition).
If Browse Repositories... is empty, perhaps something happened with your version of Android studio?
If you're on the Canary channel your build might be too advanced for plugins, for instance. At least, that's what I think my issue was, as I switched to another (older) instance and everything was fine after this
I felt a bit stupid upon realising this!!
I had the exact same issue on my Android Studio 3.6.1 but a quick restart after looking for solutions turned out to be the way to go.
I use Visual Studio 2013 Professional Update 4 in combination with multiple SQL Server 2012 Enterprise servers/instances. The Idea was to create a Version controlled deployment using a Visual Studio Solution with SQL Server Projects.
However for some reason the "Update Target" and "Generate Script" button is disabled.
I can update the local database project from the sql server database but the other way around is not working. (see screenshot)
Google is not helpful at all although I found a few people with a similar problem.
Update target button is disabled after schema comparison
VS2012: Schema compare, update button disabled
VS2012 Schema compare buttons disabled
But none of this questions/blogposts is about Visual Studio 2013 and in addition none of the proposed solutions is working for me.
Question: Why is the Update Target button disabled and what do I have to change to fix this?
Note: Of course, I'm using the latest version of SQL Server Data Tools(12.0.50318.0)
This was driving me nuts, as well. I finally noticed a "warning" message stating "Cannot generate deployment plan due to an internal error". Because of this, the Update and Generate Script buttons were both disabled.
I resolved this by closing Visual Studio, navigating to the folder containing the Database project and removing all (*.dbmdl) files. I then restarted Visual Studio, re-ran the compare schema and the Update button was enabled.
The tip that helped me was to look at the error list. (View Menu, Error List). Once I cleared the errors (just the errors, the ones with the red X) I was able to compare the schema again and the Update and Generate Scripts buttons were both enabled.
Beside the generate script, click on OPTIONS and select only the objects for which you want to compare.
This and ONLY this worked for me.
I have this Metro App project that I just tried building for the Windows Store.
After completing the buildprocess (with no errors) I can't open the appxmanifest xml file in visual studio anymore. If I select "STORE" > "Edit App Manifest" I get the following error message: "Value does not fall within the expected range."
I can't open any manifest file in any project now.
Does anybody know whats happening, do I need to reinstall Visual Studio or whats going on?
I'm pretty desperate, so any suggestions are welcome.
Found the answer here http://forums.asp.net/t/1836720.aspx/ - so i tried deleting the .suo files from the project, and now it seems to work. I have no clue why that would affect newly created/other/checked out projects, weird behavior indeed?
(Since I am both new to SO and to Visual Studio, I don't know if answering my own question is considered bad practice, if it is, please let me know what I should do instead)
It's an XML file, so you could try to open it with a text editor to figure out if there's an invalid value set somewhere. You could always compare to a default Package.appxmanifest from a new project.
Can your fellow coworker open the manifesting file you're having trouble with?
The first thing to check is to make sure you are running Visual Studio as an admin. (Right click, run as administrator)
Try creating a completely new project. Save it without modifications. Build it. See if you can open the manifesting file in that project. If you can't, try a XAML/C# project instead of JS just to see if something is wrong with the specific project type.
And before you try completely reinstalling, you might try resetting your Visual Studio settings. Make sure to take a backup just in case you need to get your environment back to where it was once you find the issue.
http://msdn.microsoft.com/en-us/library/ms247075.aspx
I'm using Vim on a Mac for front-end development and was recently hired at the company that uses Team Foundation Server as their version control system.
I would hate to have to switch to using Visual Studio on Windows because I'm so used to Vim and the Mac.
I found this and was hoping that would be a possible solution. I would still like to avoid editing code in Eclipse. However I wouldn't mind opening Eclipse to do version control stuff.
I'm very unfamiliar with Eclipse and Team Foundation Server (not VCS in general) and I need some advice on how to actually use it.
I'm able to connect to the server and find the project I have to work on, but from here I'm lost. This is the window I'm stuck at.
Anyone who are in a similar situation and could offer some help?
You've done the hard bit I think, firstly you should be able to safely ignore the Work Item and Build "folders" unless someone explicity tells you to use work items, at which point they can show you what you need to know as it works exactly the same as in Visual Studio.
If you double click on the Source Control folder it will open a new window which will show you the source "tree". To be able to Get, Checkout and add source files to the tree you'll need to set up a workspace. Once you've done this then you can get the code and check out.
With Team Explorer Everywhere You also have the option of using the tf command line in the Mac terminal. This would eliminate the need for eclipse. (I'm assuming that as a Vim user you're not afraid to use the terminal)
Another option might be svnBridge however I think you need the server version if you're using a Mac, and this requires a site to be installed in the TFS application server which might not be an option.
Finally TFS now offers support for integration with GIT.
I have a smallish utility library I made that I had created in TFS Beta 2 to test out TFS. I now have TFS rc1 installed(and Beta 2 uninstalled) and am trying to add my Solution to TFS.
I get an error saying that it is already bound to my old TFS, which was on a different system then this one. Strangely, when I go into Source Control and look at the bindings it says there aren't any. Also, I manually deleted the .vss and .vsc files and it still does it.
Ideas? I looked through the numerous other SO topics related to this but unless I missed one none of them are dealing with my issue.
Ideas?
Grab the TFS Sidekicks from Attrice. They have a workspace sidekick, you can pretty quickly find your old machine and unbind/delete that workspace from TFS.
Once you install:
VS Menu Bar
Tools
Team Foundation Sidekicks
Workspace Sidekick
Owner will defult to you, just clear machine name
Search
Select old workspace, click the red X to delete
I had old server entries too and I fixed it by using the workspace sidekick mentioned here and then using the command line to get the rest that the tool couldn't find.