https://discord.umbraco.com
Join Discord
Debugging RCL paths
# package-development
w
Anyone got any tips on how to debug why RCL paths are not working ?!
I 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 ?!
And navigating to 
https://localhost:44376/App_Plugins/Umbraco.Community.User2FA/umbraco-package.json
gives a 404 when in consuming Nuget project but like I say totally fine with a project reference ?!?
@Kevin Jump you normally have had some good tips or pointers in the past
Hmm this gonna bug me tonight...
k
hummm 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
Yeh got a targets only for the JSON schema file stuff for Umbraco consuming build to pick it up
But may be onto somethignb with nuget cache - will try bumping with a speecific build/version number to verify at lunch.
Cheers Kev !
For anyone reading or who cares. It was because I used a 
.props
file named my package in the 
buildTransitive
folder of my nuget package that collides with the one that the RCL wants to create. Solution rename my packagename.props to 
packagename.targets
(See screenshot below, compared to one above) https://cdn.discordapp.com/attachments/1260207468504547358/1260903494169268294/image.png?ex=66910363&is=668fb1e3&hm=d2880fc0cca976406e0945f8989255daeed094ee933c970bd89bd76a3948cad5&
2 Views
PreviousNext
Powered by

Umbraco

A hub and casual space for you to interact with fellow community members and learn more about Umbraco!

Powered by