Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, Power Apps, Power Automate, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
Am getting stuck with invoke CMD or PowerShell from D365 with a job. The Job seeming endless after this 'process.StandardOutput.ReadToEnd()' line.
Am tried the below attached snippet.
Any help will be appreciated. Thanks.
I think it's not caused by anything in D365FO. Please look at this discussion at StackOverflow: StandardOutput.ReadToEnd() hangs.
By the way, what business problem are you trying to solve by this implementation?
As Martin said, what is the actual business problem here? You have to remember you cannot take ANY dependency on the infrastructure.
Today it's running on Windows Server, but tomorrow it could be on server core, in a container, whatever. This seems like a recipe for future problems. Can you elaborate what you're trying to achieve? We may be able to help you find a more suitable approach.
Business Applications communities