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.

Sign up for GitHub

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

Jump to bottom

Continue to use Embedded Resources (single dll distribution) #5

Open
Hendy opened this issue Mar 1, 2019 · 1 comment
Open

Continue to use Embedded Resources (single dll distribution) #5

Hendy opened this issue Mar 1, 2019 · 1 comment
Labels
help wanted All and any feedback welcome

Comments

@Hendy
Copy link
Contributor

Hendy commented Mar 1, 2019

Should we continue with a single dll deployment or split into two NuGet packages ? (two packages would be used as the PropertyValueConverter may be needed by projects other than the website solution).

If single dll deployment still preferred, then use this package ?
@Hendy Hendy added the help wanted All and any feedback welcome label Mar 1, 2019
@dawoe
Copy link

dawoe commented May 2, 2019

I would prefer to split them. I did this for my OEmbed picker package. Previously all was handled in a single dll that had all client side resources embedded.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted All and any feedback welcome
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Hendy @dawoe