Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NuGet package #24

Open
jamiepollock opened this issue Mar 17, 2018 · 1 comment
Open

NuGet package #24

jamiepollock opened this issue Mar 17, 2018 · 1 comment

Comments

@jamiepollock
Copy link

Hey folks,
I discussed with @mattbrailsford about submitting a PR to create a NuGet package for ezSearch.

The current package supports v6 but I installed it today on a v7.9 site and it works perfectly fine. Aside from a few squiggly lines for obsolete methods.

What would you consider a sensible version of Umbraco to base the NuGet dependency on?

Thanks,
Jamie

@jamiepollock
Copy link
Author

jamiepollock commented Mar 17, 2018

So I've made some great progress with adding in the typical UMCO build for ezSearch. I settled on v6.0.4 for the Umbraco dependency.

The problem I have is the age old issue of installing the Macro, Document Type & Template like the standard Umbraco package .zip can do.

I've been looking around and the only hints I've seen so far are Shazwazza's Articulate Package. This requires people who install via NuGet to install the additional Umbraco data via a backoffice dashboard (see "Nuget" section of the blog link.

This would actually fix one of my gripes I have with the current installer is that I love the Macro but would prefer if I didn't have the template & doc type installed. I understand ezSearch should be easy and that's why they're there. :)

Anyways the point is adding a dashboard in would fragment the installer journey twofold:

  1. v6 sites would need a different backoffice dashboard
  2. nuget installers would have a different journey in than people who install it via the package repo

If we were to go down these route though I think we should make the choice to drop support for v6 if it's via nuget and choose a sensible v7 version to go with that doesn't inhibit future development.

Any thoughts? :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant