Check out the latest Commerce updates!Learn about the key capabilities and features of Dynamics 365 Commerce and experience some of the new features.
Download overview guide | Watch Commerce video
2020 release wave 1 Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
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 | Upcoming TechTalks
The last time I was able to create a build successfully for my retail deployable package was on v10.0.6 PU29..
I upgraded to v10.0.7 PU31 and now I get all these MSB3030 errors.
LCS doesn't upgrade the RetailSDK directory automatically when updating the development environment with the deployable package. sO I have to download the package to my VM and copy the folders and files under RetailSDK/Code to the RetailSDK-mirror on my Dev VM.
First I tried the Merge from RetailSDK-Mirror which got the new RetailSDK to RetailSDK-Dev. But the merge doesn't work because I got the MSB6006 error.
Then because I have to get a deployable package asap, I deleted everything in RetailSDK-Dev and copy in the new RetailSDK from RetailSdk\Code. I did copy my custom folder out first before deleting it. Luckily I don't have a lot of custom yet.
When I run the MSBuild on the new RetailSDK it builds without errors. I then open CloudPOS and because I need the PosApi in my custom, I right click it and choose include in Project. It hen rebuild the CloudPOS solution again and this time I get the error:
"C:\Source\RetailSDK\dirs.proj" (default target) (1) ->"C:\Source\RetailSDK\Pos\CloudPos.sln" (Build target) (91) ->"C:\Source\RetailSDK\Pos\Web\Pos.Web.csproj.metaproj" (default target) (92) ->"C:\Source\RetailSDK\Pos\Extensions\Pos.Extensions.csproj" (default target) (90:2) -> C:\Source\RetailSDK\Pos\Extensions\Pos.Extensions.csproj(92,5): error MSB3030: Could not copy the file "typings\DataJS.d.js" because it was not found. C:\Source\RetailSDK\Pos\Extensions\Pos.Extensions.csproj(92,5): error MSB3030: Could not copy the file "typings\KnockoutJS.d.js" because it was not found. C:\Source\RetailSDK\Pos\Extensions\Pos.Extensions.csproj(92,5): error MSB3030: Could not copy the file "typings\Pos.Api.d.js" because it was not found. C:\Source\RetailSDK\Pos\Extensions\Pos.Extensions.csproj(92,5): error MSB3030: Could not copy the file "typings\Pos.Types.d.js" because it was not found. C:\Source\RetailSDK\Pos\Extensions\Pos.Extensions.csproj(92,5): error MSB3030: Could not copy the file "typings\Pos.UI.Sdk.d.js" because it was not found.
I downloaded the deployable package for V10.0.6 PU29 and I noticed that under RetailSdk/Code/POS/Extensions the typings folder already exist with the typescript files.
Looking at v10.0.7 PU31 it doesn't come out of the box with the typings folder. The first time one runs the MSBuild I noticed it created the typings folder and copied the typescript files from RetailSdk\POS\Contracts to the typings folder. However it doesn't generate the js-files it is looking for.
The typescript DLL that comes with the deployable package is 2.2.2 and I have 184.108.40.206 installed. That was what was available for download when I started with Retail development and it worked fine while on the previous version.
When I run msbuild in the msbuild command prompt for VS2015 as administrator, it gives the same errors for project ModernPos.sln, ModernPosSetup project and ModernPosSetupOffline project.
I need to get a deployable package out but I can't get past this error.
When I add my custom POS extension into CloudPOS, it generates the js-file for my typescript file but it still gives the error that it cannot find the js-file for my custom typescript file on top of the errors on the typings typescript files.
Any help ASAP is much appreciated to get this fixed. I did log a support issue with Microsoft and added it as urgent but it doesn't look like they plan on treating it as urgent because they are supposed to respond within an hour and it is now almost 3 hours later and no response yet.
I read somewhere that the build environment must be the same version as the target environment. The sandbox that I need to upgrade is on v10.0.7 PU31. I assume I cannot put v10.0.6 PU29's RetailSDK back in and then create a deployable package.
I finally got it to work. I in the end copied some of the files from v10.0.6 PU30 RetailSDK which included the schema and typings folders in Pos.Extensions as well as the pos.extensions project.
I then again added my custom back in and this time I did not include the typings folder in my project and this time it built successfully.
I was able to update the sandbox with my custom and it worked !!!
I showed Microsoft all the trouble I have to upgrade to the next available platform. I also showed them that every time a package comes out the References directory under POS has the version number as part of the name for each sub-directory that contains its DLL. So I have to re-add every time the references to my CRT project.
Merging from retailSDK-Mirror -RetailSDK-Dev doesn't work either for me. That is when I get the MSV6006 error so that I in the end have to delete everything, even my custom, put the latest version in and re-add my custom.
This is just not working for me. So can I ask what steps do you guys take to upgrade your RetailSDK-Dev to the latest PU?
This is what I have to do at this point:
1) Download the MSFT standard application and binary deployable package that I want to install.
2) After download BEFORE unzipping the file, unblock it first.
Right-click the zip-file , choose properties.
Click in the Unblock checkbox to unblock and choose Apply, then OK.
3) Unzipping the zip-file.
4) Log into VS and delete all the files and folders in RetailSDK-Dev but copy the custom to someplace else first.
5) check it in. After checking in, merge it to RetailSDK-Main.
6) Go to RetailSDK -> Code folder and copy everything in this folder to C:\Source\RetailSdk-Dev.
7) Open MSBuild CommandPrompt for VS2105 as Administrator.
8) Run MSBuild and make sure it builds without errors.
9) Go back into VS and in source control , right-click RetailSDK-Dev and choose Add items to folder
10) Choose all the files and folders, click next.
Then choose al the files and folders in ExcludedItems tab and click on Include Items so that ZERO items shows to be excluded.
11) Choose Finish.
12) After everything was added, click on Check-In.
13) Add custom POS extensions back in.
For CRT custom, open the project, remove the references that gives now an error and re-add them from C:\Source\RetailSDK\References
Rebuild the CRT projects and copy the DLL's over to K:\RetailServer\WebRoot\Bin as well as C:\RetailSDK\References before creating a package
I mean there must be a better way to upgrade RetailSDK
Hi, it is very strange you have this situation.
SDK is usually available after packages installation in K/J:\RetailSDK\Update\ folder
I asked Microsoft and they told me they do not upgrade K:\RetailSDK but they do put the upgrade in \the sub-folder Update like you mentioned.
I checked in that folder and saw it. So at least I won't need to download it myself anymore.
What I can't understand is the naming convention of the sub-folders under References that contains the standard DLLs that one has to add to a CRT project as a reference. They change with every upgrade.
I had to "fix" my CRT project due to errors because the reference path for the DLLs suddenly didn't exist anymore after an upgrade.
So the monthly standard upgrades are going to break my CRT custom every month?
Do you go back every month to your custom and replace the references or do you keep all the different version DLLs in source control and your project just points to the one it was created with regardless if there are newer versions of it.
For example to reference Microsoft.Dynamics.Commerce.Runtime.Entities.DLL the path to it has some version number behind it which changes for every upgrade:
I asked Microsoft about the sub-folder naming convention and here is the answer.
"I asked around and in a hypothetical scenario, one customer removes the build number in the folder name and maintains it using a powershell script to rename the folder and excludes the build number.
I’ve brought it up to the product team and they are requesting you to put the change request at the Ideas site - http://ideas.dynamics.com "
So I added a change request: experience.dynamics.com/.../
Business Applications communities