Split the package onto two ones: core and bootstrapper about embeddedresourcevirtualpathprovider HOT 3 CLOSED

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...

1. You already have startup code - surely you can just delete the included cs file once it's added? It only happens when you install.
2. You say WebActivatorEx is unneeded. Is there a better way of registering the VPP?

from embeddedresourcevirtualpathprovider.

You already have startup code - surely you can just delete the included cs file once it's added? It only happens when you install

Yeah, but it's a library (package) which is installed by other people in their apps, so they will have to do additional thing.

App
 -> Lib1 (with bootstrap code), depends on VPP
   -> VPP , depends on WebActivator + installs a content script

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).

You say WebActivatorEx is unneeded. Is there a better way of registering the VPP?

In general I don't think there is another good way, but I just have my own WebActivator (forked) which
do the same.
My lib already has bootstrap logic with registering different stuff, so I was going to add just registering VPP as well in it. But I'm afraid that people who installs the lib won't notice additional script in App_Start and leave it (or do notice but don't touch it). So they'll have two registrations of VPP which is not good I believe. It's kind of dilemma what to do: keep my own registration and tell/doc that "you need to delete additional file" or just let them do registration on their own.

from embeddedresourcevirtualpathprovider.

See #38

from embeddedresourcevirtualpathprovider.