Debugging RCL paths
# package-developmentw
Warren Buckley
07/09/2024, 12:14 PMAnyone got any tips on how to debug why RCL paths are not working ?!
Warren Buckley
07/09/2024, 12:15 PMI have a project setup with a project reference and the RCL works fine, but when packed up in Nuget and consumed in a new project the RCL path doesn't work ?!
Warren Buckley
07/09/2024, 12:18 PMAnd navigating to
https://localhost:44376/App_Plugins/Umbraco.Community.User2FA/umbraco-package.jsonWarren Buckley
07/09/2024, 12:18 PM@Kevin Jump you normally have had some good tips or pointers in the past
Warren Buckley
07/09/2024, 6:14 PMHmm this gonna bug me tonight...
k
Kevin Jump
07/10/2024, 8:38 AMhummm i am not sure .
things i can remember caused me pain,.
1. Nuget caching of a package (in the local nuget package folders) - so now i always build with build numbers (eg. 1.0.0-build.20240710.1) that way i am always sure i am not hitting a nuget cache issue.
2. The name of the targets file (if you have one, and you don't necceserly need one) has to match the package name or things get confusing (e.g mypackage with a mysuperpackage.targets file causes pain).
w
Warren Buckley
07/10/2024, 8:39 AMYeh got a targets only for the JSON schema file stuff for Umbraco consuming build to pick it up
Warren Buckley
07/10/2024, 8:39 AMBut may be onto somethignb with nuget cache - will try bumping with a speecific build/version number to verify at lunch.
Warren Buckley
07/10/2024, 8:40 AMCheers Kev !
Warren Buckley
07/11/2024, 10:20 AMFor anyone reading or who cares.
It was because I used a
.propsbuildTransitivepackagename.targets2 Views