Easy way of referencing nugets
jrunestone opened this issue · 2 comments
Hi, this is looking really promising, I really struggle with the default editor so I'm going to try this out tonight thanks!
One issue with the original editor is keeping references between machines, especially nuget references. Could we add a reserved variable that points to the user's nuget folder or better yet a convention that finds nugets based on package name and version? Eg nuget:SomePackage-1.0.0. I could contribute if you think it's a good idea.
Then all we need is a simple ui that generates an npl config and we can phase out the mgcb-editor ;)
As a related update I noticed that NPL assumes that all dependencies of a reference resides in the same folder (i.e. that you reference assemblies from your bin folder i suppose). So if I reference an assembly from the nuget packages folder, it fails to build because it can't find its dependency (even if I add that dependency as a separate reference in Content.npl). Haven't confirmed by looking at the code but I don't have this issue adding the references in the MGCB editor. Isn't that weird, all NPL does is write the mgcb config?
EDIT: Sigh I think it yet again boils down to the MGCB editor being the way it is.. not sure it's even possible to have references to absolute paths.. I guess I'll have to point all my references to the bin folder :(
Sorry for opening and closing but this should really be fixed in the mgcb editor instead.