Breaking news from around the world
Get the Bing + MSN extension
Check out the latest Retail updates!Learn about the key capabilities and features of Dynamics 365 Retail and experience some of the new features.
Download overview guide | Watch Retail video
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
Hello community, This question is about development / debugging D365 Retail CPOS / MPOS extension code. Here is the technical background :
Question n°1: Does anyone know how can we load the "Pos.Web" project on a cloud hosted DevBox with administrator rights ?I'm asking this because the only procedure that I found is marked as for DevBoxes without administrator rights.
Question n°2: How should we debug POS extensions, by pressing F5 or by attaching to process (w3wP or iisexpress) ?
Question n° 3: Should we put the break points in the .TS files or in the corresponding .JS files generated automatically ?
Questions n° 4: Did anyone actually create a CPOS / MPOS extension and debug it with Visual Studio ?If yes, could you please share some detail on how to achieve this “miracle” ? :-)
Thank you. Kind regards,Saso
Hello Saso Gligor,
CRT extensions - you need to attach to the w3wP process.
TS files - you need to press F5. In some cases, breakpoints are not loaded. For that, you need to set a breakpoint in the Pos.js file.
Thanks a lot for your answer.Yes, you are right:
I have worked out all of the answers on my initial questions.Let me summ them up and post them in a usefull manner :-)
Have a nice day.Kind regards.Saso
Here is an update of my initial post, as I managed to resolve pretty much everything. The following solution worked for me, which doesn’t mean that it's 100% sure. Don’t hesitate to question.
Does anyone know how can we load the "Pos.Web" project on a cloud hosted DevBox with administrator rights ? I'm asking this because the only procedure that I found is marked as for DevBoxes without administrator rights.
On a freshly deployed environment, when you try to load the “CloudPOS” solution you will probably get the following error:
In order to load the "Pos.Web" project, it doesn’t matter if you have or not administrator rights on the DevBox, you should edit the “Pos.Web.csproj” file and replace the tag value of <IISUrl> with the URL of your POS server.
You can find it in the LCS details page of your environment => Login => Log on to CPOS. After changing this tag value, the project can be loaded.
So at this point everything is working well. If we then try to debug our project by clicking F5, we will be asked to enable debug mode in “Web.config” file, as shown here below.
After that, the debugging of the “CloudPOS” solution was impossible for me. When I start debugging with F5 or “Attach to process”, I always got the following error:
No need to mention, the “MSVSMON.EXE” service was running correctly, so that was not the problem really. I was looking for something else. By changing the following in the "Pos.Web" project, I managed to go around this problem, tag value of <UseIIS> from True to False.
After these changes you get the following error, which is in fact the one that the Microsoft article starts with: https://docs.microsoft.com/en-gb/dynamics365/retail/dev-itpro/cloud-dev-box
At this point you can apply the procedure in the above article, which will enable you to start the application with pressing F5 and debugDebuging exclusively with Internet Explorer, it does not work with other navigators,
How should we debug POS extensions, my pressing F5 or by attaching to process (w3wP or iisexpress) ?
CloudPOS: I managed to debug my extensions with running the application in debugger mode. Press F5 and before doing so I check that the default navigator is “Internet Explorer”. The last thing is very important, POS extension break points don’t get hit in any other navigator then “Internet Explorer”.
ModernPOS: I managed to debug my extensions by running the ModernPOS application, and then attaching the debugger to the “iisexpress” process.
Should we put the break points in the .TS files or in the corresponding .JS files generated automatically ?
Break points in TS files get hit when using the above approach. Break points in JS files don’t seem to get hit in POS extensions, no matter the approach.
Did anyone actually create a CPOS / MPOS extension and debug it with Visual Studio ?If yes, could you please share some detail on how to achieve this “miracle” ? :-)
Yes, me, please read myself above :-)
Kind regards, Sašo
Business Applications communities