Delete team project from Visual Studio Team Services - visual-studio-2012

I am using Team Services on domain visualstudio.com and I need to delete one project, I found out that I need to use command prompt to delete projects, but when I tried the script it seemed that it doesn't work
My Script is,
TfsDeleteProject
/force collection:https://mytfs.visualstudio.com/DefaultCollection MyProject
My first mistake was that I didn't append DefaultCollection to the URL, but now I get error that I don't have privileges.

Thanks to #Christopher I was able to make the script work.
You can use the following command from the "Developer Command Prompt":
TfsDeleteProject /collection:https://mytfs.visualstudio.com/DefaultCollection MyProject

You can now do it via visualstudio.com
Open the administration context for the team project collection by choosing the gear icon.
Open the menu for the team project that you want to delete.
If you don’t see the actions icon , either you’re not accessing VSTS or you’re not a member of the Project Collection Administrators group.
You must type the name of the team project in order to initiate the delete operation.

Open “Developer Command Prompt” under “Program Files>Microsoft Visual Studio” or in Windows 8 type “Developer“.
In the command prompt, use this command template below to delete your project from TFS. Replace the YourTFSName to yours and also the ProjectName to the name of your project.
TfsDeleteProject /collection:https://YourTFSName.visualstudio.com/DefaultCollection ProjectName
Hit Enter and then Y if you are prompted for confirmation.
Done. Double check by login to your TFS online.
From http://bizvise.com/2013/03/08/how-to-delete-team-project-from-my-team-foundation-service-tfs-default-collections/

Although the accepted answer is absolutely correct and very clear, I managed to get lost and run into that 'grayed out Delete button' issue and just wanted to share what I was doing wrong.
For the folks having issue with grayed out delete button, make sure that you are inside 'View the collection administration page' (as shown in the accepted answer), not inside the project itself.
If the last breadcrumb on the top of your VS Team Services is the name of the project, you are at the wrong place (it looks similar). Here the Delete button (appears on right clicking the project name) will be grayed out.
If you click the link that says 'View the collection administration page' after clicking the Settings(gear), you will be at the right place.

if your project name have space, you must use "MyProject name"
TfsDeleteProject /collection:https://mytfs.visualstudio.com/DefaultCollection "MyProject name"

Related

Unable to publish customization from Customization Project Browser screen

I am having a weird case where I am unable to publish customization from Customization Project Browser. Whenever I click on Publish Current Project menu item from Publish menu, it opens up Compilation immediate window with Publish Customization heading but then it just stuck there with no further process.
But, I can publish the same project from Customization Projects Screen where I select the Customization Project with checkbox and click on Publish action icon.
Currently, that's the workaround I am using to publish but is there any other way that I can do to fix this issue?
I have cleaned up ASP.NET Temporary Files and Acumatica's Apply Updates.
Thanks.
that's due to some update in .net framework.
the solution is to update acumaticaERP to the latest, or do some workaround.
publish from custom project form
edit web.config and add <add key="aspnet:DisableAppPathModifier" value="false" /> to appSettings
https://community.acumatica.com/customization-and-development-72/after-the-installation-of-the-2020-10-cumulative-update-for-net-framework-3-5-and-4-8-users-were-unable-to-publish-a-customization-project-from-the-customization-project-editor-3854
I discovered the reason for this strange behavior, as well as the solution. It happened to me as well.
Reason: the w3wp process encounters an error during publishing. The folder permissions for c:\Program Files\Acumatica ERP\TemporaryAspFiles[yourAppName]
have been removed or deleted for the speficic windows account, which is used by the ERP, and the temporary sub-folders can't be created without create permission. I can't see how it happened, but I noticed the strange behavior occurred after the last "major" windows update. See the screenshot for the proof.
Solution: re-apply the user account security for your application folder. That is how I fixed the publish problem on my end.

How do I delete a solution from TFS 2012

how do I delete a Team project from TFS?. I am using VS2012.
The situation is that a Team Project was created with the wrong name, and another one was created with the right name and all the code has been checked into that.
I just want to delete the wrongly created one. I cant find any specific help on this, although there are articles on how to do it on if your TFS is hosted on visualstudio.com.
Apologies if this is a noddy question but I have looked for the answer and cant find it...
Thanks in advance
Jonathan
You can use the "TFSDeleteProject" command line tool to delete the team project.
Here is the usage:
TFSDeleteproject [/q] [/force] [/excludewss] /collection:URL TeamProjectName
TFSDeleteProject permanently destroys the team project, after which it cannot be recovered. You should backup all important project data before using TFSDeleteProject.
Required permissions
To use the TFSDeleteProject command, you must be a member of the Team Foundation Administrators security group or the Project Administrators security group.
You can use the link to delete the team project using the administrator console.

Visual Studio 2012 Build Process Template Dropdown does not populate

My issue is that I cannot select a build process template after migrating to TFS/VS2012.
I managed to google and find one article which suggest the same problem here,
Possible Bug
Any ideas how I can get the dropdown to load the Build Process Templates or why they may not be getting loaded?
Also, I am able to click New->Copy Template, and copy successfully, but it never populates the dropdown list after accepting.
Possibly the same issue
I recently ran into the same problem but not related to upgrading the server. We were not able to see build process templates when trying to add a new build definition. We are in TFS 2012. This team project also appeared not to have any build definitions. That was expected though because we had not yet used the TFS builds on this team project.
The problem was caused by someone with admin rights setting the "View build definition" and the "View Builds" access rights to Deny for everyone.
By just setting that back to allow on the TFS group, we suddenly could see the build definitions and also were able to select build process templates.
It was really strange that it let us add new build process templates, but we couldn't select them.
Sooo...
I was finally able to get the templates loading by doing the following.
Unmapped the entire TFS project which had been mapped in a sub folder and not at the root.
Deleted files from disk completely
Remapped the TFS project, this time from the root TFS project level
Accepted the "get"
After doing this my build definitions loaded and worked. (Seems to be a mapping issue...bug...)
This may be an extream solution and I am still not sure what happened but it now works.

Unable to shelve changes in VS2012 for TFS2010

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.

How to upgrade a part of a package/solution (customwebform, workflow, etc.) without losing list items

I've been developing a new SharePoint 2010 package in Visual Studio 2010. This is my first development project in SharePoint so please pardon my use of incorrect terminology.
Within the package/solution there are a couple of Features, a couple of custom web forms, and a workflow for the custom list type which is also within the solution.
To develop and debug I've been simply using the Build > Deploy Solution option from within Visual Studio to build the solution and then it would automatically connect to my sharepoint server and create the custom List, install the features, add the workflow, etc.
But when I want to make a change, say change the color of the text on the custom NewForm (mine is called MyCustomForm.ascx) then I click Build > Deploy Solution it deletes the custom list, deletes the workflow, deactivates and deletes the features and then re adds them all again. Thus I lose all of my list items.
In production if I need to modify the workflow I can't simply do this as we would lose all of our list items. How can I do this?
I've done days worth of research and nothing works. I've looked into:
stsadm -o upgradesolution -name SharePointProject1.wsp -filename ...
stsadm.exe -o execadmsvcjobs
with no avail. It says everything "works" fine (no errors) but doesn't update the custom MyCustomForm.
I've also tried manually editing the files in:
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\CONTROLTEMPLATES
to no avail as well. I modify the MyCustomForm.ascx file and refresh the SharePoint site page and it hasn't changed.
Any insight would be helpful. I am doing all development on the server machine that is running SharePoint and have admin access if that helps. Thank you in advance for all of your help.
The list is deleted because the solution package that you're deploying has the list item in it so Visual Studio is "helping" by making sure that you get the lastest version of everything (even it it hasn't changed)
There are two approaches you can take to over-ride this behaviour
Set the deployment model to "No Activataion" this will result in the package being deployed and leaving previously deployed and activated feature in place.
Remove the list instance item from the package by double clicking on the Package in the Solution Explorer and then double clicking on the List Instance Item in the right hand pane.
Next time re-deploy the solution you not should have your existing list removed (I'm not 100% on the workflow association behaviour).
Of the two I'd lean towards option 2

Resources