I do have two visual studio online accounts:
mypersonalaccount.visualstudio.com (free basic) and
mycompanyaccount.visualstudio.com (paid)
I started a small project into my personal one a few years ago. Now this project grows up and we create a little company.
I would like to change this project from my personal account to the my company account. in order to take advantage of the paid features.
How can I migrate a project from one account to another?
I would like to change the ownership for all data, no just the code repository but all tasks and sprints data too.
There is no such tool provided by Microsoft. Microsoft supports the migration from Team Foundation Server on premise to Visual Studio Team Services.
What I would suggest is to either use alternative tools like the vsts-sync-migration, or write your own PowerShell scripts leveraging the VSTS REST APIs to move the data you need.
Related
I am given a sharepoint location from my organization. I have to save my Visual Studio project onto this location and use it as a repository/TFS/AzureDevOps like integration where my team members can access the project, map them to their space and work on the project.
Please help on this
Agree with #Daniel Mann. SharePoint is used to share and manage content, knowledge, and applications to empower teamwork, quickly find information, and seamlessly collaborate across the organization. SharePoint isn't designed to be a source control tool for code. Based on my knowledge, it won't integrate with any IDEs, and it does not have customized GUI to manage source control code, etc.
There are many version control tools, like Azure DevOps Services, which can host unlimited free private repos and start free.
What tools are you using for CRM plugin development?
I used both "Dynamics 365 Developer Toolkit" and "Dynamics 365 Developer Extensions" previously. Unfortunately, The "Dynamics 365 Developer Toolkit" no longer works reliably for me in VS 2019 (yes, I followed the steps to update the vsix file). I looks like Jason Lattimer's has stopped making the "Dynamics 365 Developer Extensions".
Thanks!
Personally I use none, but rely on an Azure DevOps pipeline to deploy everything.
For client side development I heavily use Fiddler 4 with auto responder rules with a local webpack devserver. I am not sure how to improve this process much more.
For serverside Plugins I prefer using ILMerge Build Tasks (check nuget) and separate the IPlugin interface implementation from my code so I can easily write unit tests for that. I do not use testing libraries like EasyRepro or XrmFakeEasy. I don't think they add a big benefit and more or less negate one of the best effects of unit testing. Creating good testable code.
For plugin deployment I currently use spkl by Scott Durrow and it is working fine so far.
For generating early bound classes I use a custom .bat file that actually just calls the CrmSvcUtil.exe with a couple of extra .dll files that helps creating enums instead of optionsets.
I am not a huge fan of toolkits or templates that dictate how you have to write your stuff, because most of them embrace bad programming patterns. For example the XrmToolkit forces you to use a certain folder structure for your clientside scripts to not mess up your crm system and so on.
XrmToolkit is a commercial Dynamics 365/CDS development add-on that is actively maintained and supports Visual Studio 2019.
I have been relying on it for years to assist with generating proxy classes, registering and publishing plugins, publishing web resources on save, etc.
I have no affiliation with XrmToolkit.
You can use Microsoft.net framework with visual studio or visual studio code for implement dynamics 365 plugins and register that in plugin registration tools.
• Write a plugin
• Register a plugin
How can one migrate from Visual Studio Online to an on-premises instance of TFS (version 2017)?
Ideally I'd like to migrate all code, project management data, etc.
Thank you for your time
There's no way to do this without the use of third-party tools, all of which will result in some amount of data loss.
There is currently no way to move from VS Team Services to Team
Foundation Server or to export a project or project collection in such
a way that it can be attached to a TFS server.
Depending on what features of VS Team Services you're using it may be
possible to migrate some of the data to a new target environment with
relative ease. And depending on what you're willing to lose you may be
able to migrate some other bits easily as well.
There are 3rd party tools that offer migration to and from VS Team
Services, though these can be pretty expensive.
Refer to this thread for details: Move from VS Team Service to an on-premises TFS
I work from a small IT department and I'm pushing to move from our current TFS implementation to Visual Studio Online. My boss who gets the final say is hesitant because "What if Microsoft decides to stop offering the service, without notice, or their servers fail how will we get our code". While I find such a scenario unlikely and the scenario of our TFS server crashing and burning with no backups/bad backups much more likely. I still need to address his concern.
Does anyone know of a way to "backup" a remote TFS implementation? So far the only thing I've come up with is doing a nightly pull of Visual Studio Online and submitting it to a local repo, feels hacky, feels wrong.
Take a look over at the discussion on this StackOverflow question: Is There A Way To Backup Visual Studio Team Services Projects?
Here is Richard's answer:
There's no out of the box backup ability.
Now, if you are only referring to source control, and not work items,
pull requests, builds, test plans or anything else that the service
offers, then I'd suggest you migrate your code over to git.
With git every developer will have a complete copy of the source
repository, including all history and commit comments. From there,
it's a simple task to push the git repository to a different git
hoster (such as bitbucket or github) and make them your new centrally
hosted git repository.
On a historical note, Visual Studio Online at one point offered a data
export for a period of time. You might want to add a vote or three to
this related UserVoice idea to help raise the importance of the
feature with Microsoft.
Side comment: The business risks in using Visual Studio Online will
come from either Microsoft shutting down the Visual Studio Online
service or that the underlying Azure infrastructure has such a
catastrophic failure that your Visual Studio Online account is
unrecoverable. Both of those are extremely low risk, and very likely
lower than the risks you'd have running TFS on-premises, in your own
data centre, unless of course, your infrastructure and staff are
better than Microsoft's :-)
I agree with Richard. Visual Studio Online is not going anywhere :) You can also use tools like OpsHub, TaskTop, and Kovair to setup a two-way synchronization or use the TFS Integration Platform to do the same thing if you really wanted an option. If you are using Git repositories, you can clone the repository into other locations to maintain multiple copies. All of those options take effort.
I posted the same answer to this stackoverflow question.
We developed our own VSO backup tool. We scheduled it as a scheduled task and it runs once a night. It then
just clones all our repositories to disk.
Taken from this blog:
We use the VSO Rest API to query our VSO account and get all the data
we need. Since in VSO you can only have one Team Project Collection,
we retrieve all the team projects of the default collection. Each of
these team projects can have multiple repositories that need to be
backed up. A folder is created for each team project and saved to a
location on disk that can be configured in the app.config. When the
team project folder is created, the task loops over each repository in
the team project and creates folders for each repository.
You can also fork it on GitHub here
We have single server with VSTS 2010.
can we install one VSTS and use with two different users in the same time ?
what is happen is this :
User_B can open projects from User_A but it time he need to change something
jump windows and asked to save the project..(*.sln file)
It sounds like what you are doing is probably a license violation.
Also, this is really not the best way to go about multi-user software development. If you have more than 1 developer working on the same project - you need some form of Source Control. There are plenty of best-of-breed free/open-source version control systems (subversion, git, mercurial, to name a few) you can use.
Developers should each develop on their own machine, and then check-in changes to a source control system.