I am hosting a project in visualstudio.com and what I have is only a VS studio 2012 installed. My friend has checked out and locked a file and then re-installed his windows, also creating a different name for his computer and thus he cannot check it in. Is it possible to remove that lock in any way? I am the one who created the project, so I should have all admin rights. It's just I do not know how to do it. I tried using
tf lock /lock:none /workspace:FRIEND-PC;friend#email.com filepath/filename.css /collection:https://***.visualstudio.com
however it seems to be searching in my computer which is not what I want at all. Nothing better I was able to find though :(
I had this trouble too. I couldn't get the commands to work without errors. What did work for me was much simpler.
From within Visual Studio 2012(and 2013):
File -> Source Control -> Advanced -> Workspaces...
In the dialog that came up, I checked "Show remote workspaces" and the locked workspace came up in the window. I then selected it and clicked "Remove".
try
tf workspace /delete FRIEND-PC;friend#email.com
Deleteing the old workspace will remove any pending changes or locks.
Here's what I did to remove the lock
tf undo /workspace:USER;Domain\User xyz.cs
I was able to remove the lock this way:
C:\Users\****\Documents\Visual Studio 2012\Projects>
tf undo /workspace:FRIEND-PC;friend#email.com
/collection:https://xxxx.visualstudio.com/DefaultCollection
$/xxxx/ProjectFolder/ProjectName/filepath/filename.css
Related
While working with some projects checked out from Git, we get errors with modifying the project settings in MyEclipse. I am trying to modify the deployment values in my workspace and it is not letting me (screenshot below).
There isn't a lot of information to go on, here (e.g. what is the version of MyEclipse, what type of project is this, what properties page are you switching from, the OS and version, whether this has worked before, the error log - but please don't paste that in here - and so on).
However, here are some actions that might help resolve it:
Firstly, try a fresh empty workspace then import the project from the old workspace, or better still import again from Git. This would help clean up possibly corrupted settings in the workspace.
Another thing to try is to launch MyEclipse with the -clean option (just add that option to the top of your myeclipse.ini file, found in the installation folder).
#Howlger is right, though, this is a commercial product and we may be better able to help if you raised the issue in the MyEclipse support forums.
I have my source code in TFS.
The issue is that when i try to get the latest files from the TFS, I am made to wait for 5 minutes for connecting to server to get. and then it says timed out! Then i will have to connect to the TFS again.
Still not able to get the code!
I had tried mapping it to a different folder but even that failed.
I am using Visual Studio 2012 Express for web.
I have already tried clearing all the local data, cache and all that kind o stuff. I even tried resetting the user data.
Also tried logging in with another account to check weather if it was an issue with my Hotmail account(it's not. because i am not able to get it even with another Id).
Nothing helped!
Issue Fixed!
Here are the steps i did to fix it.
Since clearing all files may reset all your settings on visual studio, this should be the last possible option to do.
Just did a repair on the VS 2012,
cleared everything from
C:\Users\(Username)\AppData\Local\Microsoft\Team Foundation\4.0\Cache
Clear everything from
C:\Users\(Username)\AppData\Local\Microsoft\VisualStudio
Clear everything from
C:\Users\(Username)\AppData\Local\Microsoft\VSCommon
But here is another issue.
I had added a file by mistake to a different repo. I have deleted that from the server(Online). but the deleted project file is still shown in my source explorer in VS with a plus sign! How do i remove those?
if anyone have any idea, please help! Thanks a lot..!
Seems your project file still have some source control bindings. So that file can be detect as new add file in source control explorer. You need to remove source control bindings.
There is a tool to remove Source Control Bindings from Visual Studio Solutions and Projects from msdn: Remove Source Control Bindings from Visual Studio Solutions and Projects Detail steps as below:
Delete the .suo next to the .sln file, and then opened the .sln file in Notepad and deleted this entire section:
GlobalSection(TeamFoundationVersionControl) = preSolution
SccNumberOfProjects = 2
SccEnterpriseProvider = {xxxxx}
SccTeamFoundationServer = http://some-other-guys-tfs-server/
SccLocalPath0 = .
SccProjectUniqueName1 = xxDemo\\xxDemo.csproj
SccProjectName1 = xxDemo
SccLocalPath1 = xxDemo
EndGlobalSection
Save the .sln in Notepad and then open in Visual Studio.
More ways and more information for you reference: How can I completely remove TFS Bindings
Solution for the second question!
It was a misunderstanding of the pending Change.
I had deleted the folder from the server but the file names still appeared on the TFS source explorer on VS.
It was just because VS did recognize it as a pending change to be checked in even-though it wasn't one!
So just an undo pending changesdid the trick for me!
In TFS server have you set all privileges (access) for your account. If not then add Administrative access for your account on TFS.
We are using TFS2010 (for source control only), and until recently everyone was using VS2010. Our developers just installed VS2012.
Pulling down code works fine in Visual Studio. When you go to "Pending Changes" in Team Explorer, we are seeing TF201072: A user or group could not be found. Verify that the users and groups used in your work item type definition have been added to Team Foundation Server., twice, at the top. We can still check-in code from VS - seems this error is ignored.
However, we are unable to shelve changes - when you attempt to shelve, the same error comes up in a popup, and the shelveset is not saved.
We can shelve using the command prompt (tf shelve), and can still shelve using VS2010, so it doesn't seem to be a permission issue. Also, the TFS administrator is not seeing the error message, and can shelve from VS2012 with no error.
Any thoughts as to what could be causing VS to error out here? We've tried clearing out the TFS cache, creating a new workspace, and gone over every option we could find in Visual Studio.
I had the same issue. Tried many different stuff from web sites and non of them helped. Finally find the solution for this. Follow these to make it work:
1) Create temporary AD User
2) You will need to transfer all old user configuration into a new temporary account. If you are OK with using the temporary account you may just keep it and get rid of old account. Go into the machine that TFS is installed and Run this command: TFSConfig identities /change /fromdomain:mydomain /todomain:mydomain /account:oldAccount /toaccount:temporaryAccount
(TFSConfig is in C:\Program Files\Microsoft Team Foundation Server XX.0\Tools\)
3) If you don't want to use temporary account you will need to convert from temp account to your old account. To do that run the same command wit changing the user names:
TFSConfig identities /change /fromdomain:mydomain /todomain:mydomain /account:temporaryAccount /toaccount:oldAccount
That's all you need to do.
I have exactly the same site settings in coda 1.7.4 as I do in coda 2 but when I click the publish arrow in coda 2 it tells me "Set both local and Remote paths in a site to publish your changes".
I have already done that but it still is not working. As I said the same settings are in the older version and it works fine and publishes.
Anyone have any of the same problems.
I contacted Coda support for exactly this issue today... Same as you, after setting up a site with the correct remote and local roots - confirmed because I could connect to both - but still the publish window said "Set both local and Remote paths in a site to publish your changes".
Literally the solution was to close Coda down and re-open it. Apparently this is a known issue, when setting up a new site you have to restart Coda to use the publish functionality.
Just by closing Coda and restarting it the publish function now works for me.
I had this problem and none of the above worked. I got the following reply from the team at Coda and it worked a treat.
Right click the saved site in question and choose Edit. Disable publishing and automatic indexing.
Save and close the site
Open the site, then from the menubar choose File > Sites > Rebuild Site Index
After the indexing competes, restart Coda and then re-enable publishing (and optionally, automatic indexing)
I had the same issue until I ticked the "Use Publishing" in the site settings.
Check out the image: CODA 2 Site Settings
I can now publish via the ⌥⌘P on a Mac.
I hope this helps.
Specifically, you have to close all the open documents in Coda, reconfirm the local and remote directories configured for the site, then close Coda2 and reopen it.
Honestly, that a bug like this still exists, is amazing. After all these years, I still need to keep Dreamweaver around. Get with it Coda! #coda #coda2
My "fix" (this time) was:
to edit the FTP server's domain to be not working,
open the site,
let it complain the server is wrong,
close Coda,
reopen Coda,
fix FTP domain,
open site,
and voilà!
A classic I-learn-by-complaining case. ;-)
(Coda 2.6.10...)
I had a situation where the publishing had been working ok, and then mysteriously stopped.
I tried all the suggestions previously answered by BenLeah, Ben Darlington, Robert Barrueco, and Manu, and upgraded to the latest version of Coda2 (from 2.6.9 to 2.6.10), but none of these restored publishing.
What did finally work for me, was to physically delete the site connection panel in Coda2 and create a new site altogether (with the exact same settings). Not sure if this will work again if the publishing turns itself off again in the future, or if it solves the problem for anybody else. If it ever does, I'll update this answer.
It's unbelievable that Panic has not fixed this by now.
Finding and deleting every Coda related file and reinstalling Coda did not help.
My "fix" (this time) was to delete the site in Coda and recreate it.
Publish stopped working for one of my sites, but for entirely different reasons than others have discussed here. I used Time Machine to roll back to a recent version of the site, renaming the original folder so I would know not to use it. Coda 2, however, kept pointing to the original (renamed) folder.
So it seems Coda uses a unique ID to identify the local root folder, not a simple file path. This is probably a good idea in most cases—it means if you move or change the name of this folder in the Finder, Coda still knows where it is. But if the actual folder changes (as it will if you recover from a backup), you can expect the unexpected.
I still don't know why the publish feature stopped working with the renamed folder. (In some ways I'm glad it did, as it stopped me publishing from the wrong folder.) All I know is that updating the 'Local Root' of the site fixed the problem.
You have to set the FTP putting the mouse on the file between your site and the page. Below the menu, as soon as you click file you will open in the middle a screen. Then you put in your FTP settings.
During web application creating i got below popup message:
"Visual studio does not have permissions to read the template information from the registry. this is often caused by registry permission problem."
Any one have any solution?
Please help me. i wana to see Visual Studio new features.
Thanks
this might be quite late as an answer, but I excpierienced the same problem and I found the solution on a msdn page : here is the original solution message :
I came across this issue with Visual Studio 2010 and Windows 7. I did not find this problems source as of yet but, I have found many Visual Studio users encountering it. I tried Michael's solution to this problem and it did more damage then anything else. It even went as far as to make Visual studio to boot into "Shell mode" and tell me the registration was not valid.
Using System Restore I rolled back the changes made by the subinacl tool and Michaels script (it probably was not meant for Windows 7, causing the errors in the first place) .
being a long time visual studio user and a pretty good trouble shooter, I knew the subinacl was the proper tool to correct the problem, but the script was incorrect for my perticular setup. I adjusted the script as follows: (this is a batch script)
cd /d "%programfiles% (x86)\Windows Resource Kits\Tools"
subinacl /subkeyreg HKEY_CLASSES_ROOT\VisualStudio* /setowner=domain\user
subinacl /subkeyreg HKEY_CLASSES_ROOT\VisualStudio* /grant=everyone=f
/grant=administrators=f /grant=system=f
pause
I tried to include the "setowner" command with the grant commands (on the same line) but it would throw errors all the time.
This script fixed MY "Requested registry access is not allowed" with Windows 7 and Visual Studio 2010.
if you want to try this script: Follow Michael's instructions, but use the script provided in this post and replace the "domain\user" with the proper credentials. You may also need to change the Path of Windows Resource Kits if you installed it in a diffrnet place or are not using a 64 bit OS. Before using this script please backup your registry.
I hope that that helped!
*the original web page was : http://social.msdn.microsoft.com/Forums/en-US/c273b0e1-7f46-4065-afaf-4edf285d2531/vista-wpfapplication-requested-registry-access-is-not-allowed
I had this problem too. Followed the post by user2698666 without success. Stuck Process Monitor on it and found there were more registry entries causing a problem called WDExpress. Thought I'd post my fix incase anyone else has same problem:
subinacl /subkeyreg HKEY_CLASSES_ROOT\VisualStudio* /setowner=domain\user
subinacl /subkeyreg HKEY_CLASSES_ROOT\VisualStudio* /grant=everyone=f /grant=administrators=f /grant=system=f
subinacl /subkeyreg HKEY_CLASSES_ROOT\WDExpress* /setowner=domain\user
subinacl /subkeyreg HKEY_CLASSES_ROOT\WDExpress* /grant=everyone=f /grant=administrators=f /grant=system=f
I had the problem with Visual Studio 13, where i wanted to add a webtest project for my newly created solution.
Tried the above trics to set ACL but it didn't work.
Finally used the Procmon.exe to locate what visual studio was doing (Include only process name devenv.exe) and look for result Access Denied. It will tell you what registry key is not accessible.
In my case it was the regkey HKCR.webtest (HKEY_CLASSES_ROOT.webtest) that caused the problem. Taking ownership and assigning acces to this solved my problem.
I do not know how the root cause of the problem.
The above didnt work for me as I kept being denied in regedit even though i was admin.
I found this on another site:
psexec -i -d -s c:\windows\regedit.exe
psexec is available from Microsoft here
http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx
This gave me full registry access. I tried to give admin owner to specific keys like above but VS 2012 express was still throwing that registry permission error. So I finally just added Administrator to the permission list of the entire HKEY_LOCAL_MACHINE\SOFTWARE\Classes\ directory in regedit. Then gave admins full control.
This worked. I can now create a project without that infernal error!
This issue has nothing to do with permissions in the context discussed. The issue is caused by an incorrect path to the template files in the registry due to sloppy installation program testing by Microsoft. The incorrect path throws an error when a user tries to start a new project and, true to Microsoft style, displays a generic and meaningless error message about permissions.
Here's the issue specifically. In some machines (assuming C: is the primary drive and user1 is the user's login name and version 2013) the location of the template files is C:\users\user1\my documents\visual studio 2013\projects. Unfortunately, the installation path written by the installer in the registry is C:\users\user1\documents\visual studio 2013\projects. So, it's pointing to \documents while the correct location is \my documents. To be sure, look where your visual studio 2013\projects folder is located - either documents or my documents - and change the registry key to the correct location.
For my example the key is at HKEY_CURRENT_USER\software\Microsoft\VisualStudio\12.0\NewProjectDialog\MRUSettingsLocalProjectLocationEntries the path is located in the Value0 entry. Check it and change to make it point to exactly where your project folder is.
Lars Meldgard's use of ProcMon was a good tip and helped me. I just wanted to include a picture of what an access denied looks like in ProcMon. I had to do it one registry key at a time--this wasn't the only one. It was very cumbersome and slow, but I was able to knock them off one by one and give full rights on each one. (That part is a hassle too, because I had to take ownership, then close regedit, then go back in so I could set the permissions; you can't do it all in one fell swoop.)