-
Notifications
You must be signed in to change notification settings - Fork 42
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
Split the package onto two ones: core and bootstrapper #35
Comments
Hi. I'm thinking about this. I don't really want to add a second package if we can avoid it, so lets go a bit deeper...
|
Yeah, but it's a library (package) which is installed by other people in their apps, so they will have to do additional thing.
As I understand NuGet will install VPP into the app as transitive dependency (honestly I didn't verify that NuGet installs content files in such a case, but it should).
In general I don't think there is another good way, but I just have my own WebActivator (forked) which |
See #38 |
Hi.
I want to use the lib as a dependency in my lib but I already have other startup code in that lib (registered callback via WebActivator) so additional App_Start script is unneeded. Moreover EmbeddedResourceVirtualPathProvider brings another dependency into app project (WebActivatorEx) which is also unneeded.
What I'd suggest is to split the package onto two ones: the first one - "core" - is implementation (lib) without any dependencies and content scripts and and second one - "bootstrap" - is a package with dependency on "core" package, WebActivatorEx and content scripts.
What do you think?
The text was updated successfully, but these errors were encountered: