According to Microsoft documentation, integration between TFS and MS Project is deprecated from VS / TFS 2019 forward. Can u please let us know what the alternative solution is to sync between gants in MS Project and TFS. Thank u
From Microsoft Documentation :
Starting with Visual Studio 2019 and Azure DevOps Office® Integration 2019, support for Microsoft Project is deprecated. Project integration and the TFSFieldMapping command aren't supported for Azure DevOps Server 2019 nor for Azure DevOps Services. However, full support for Microsoft Excel integration is maintained.
As stated in the documentation: full support for Microsoft Excel integration is maintained. So to support your work tracking work, you can use Microsoft Excel as an alternative. To work in Excel, see Bulk add work items with Excel.
Working in Project is similar to publishing and refreshing work items using Office Excel, with a few differences as described in this article.
According to the differences between Project and Excel, Excel is more superior than Project.
Though Excel doesn’t have a predefined Gantt chart type, you can create one using this free template: Gantt project planner template for Excel.
Related
In Microsoft Project 2016.
To see a list of published Microsoft Store Project Add-Ins: Project Tab, Get Add Ins, Store, Project Management. Workday Projects Integration is an example of a published App.
What is the Visual Studio development and publishing path and is there a reliable, current template/tutorial etc?
thank you
Stew
Image showing MS-Project Add-ns chosed from MS Store
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 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.
Friends,
I am trying to setup Continuous Integration with Azure WebJobs. I have a Web and a WebJobs project in the solution. I have continuous integration and deployment already setup for the web app in Visual Studio Online (*.visualstudio.com).
I also connected the WebJobs and the Web app using the Visual Studio ASP.Net extensions - Right click the WebSite project in VS 2013 > Add > Existing Azure WebJob project. It created webjobs-list.json file in the website project.
I was expecting that when the Web app deployment happens to Azure Website after the Visual Studio Online build, it will deploy the WebJobs too. But it is not doing so.
How do we automate the WebJobs deployment after Visual Studio Online build in visualstudio.com?
The WTE team is aware of the TFS publishing issues. I've been personally working on developing a workaround with which I'm comfortable but haven't finalized it yet. My team is working on an improvement to the WebJobs publishing experience from VSO. This item is absolutely on our agenda to repair, and will be included in the next VS update. In the meantime I'm trying to come up with a workaround for the time being; once that workaround is prescriptive enough to post, I'll write a post summarizing the process on our team blog.
This looks like the way to do it with VSTS
https://blogs.msdn.microsoft.com/tfssetup/2016/05/18/deploying-and-schedule-azure-webjobs-from-vsts-to-azure-web-app-with-bonus-cron-scheduling/
Basically,
Use VS to link your web job to a web app.
Create a new Buildtask that uploads the WebJob.zip file.
Profit.