Nuget install.ps1 remark

Topics: Bootstrappers & IoC, Extensibility
Feb 20, 2012 at 6:49 PM

Caliburn.Micro package should not always add an AppBootStrapper, ShellView.xaml etc to the project it gets added to, more specifically when the package is added to a library project... e.g. I have two libraries containing some of my own framework extensions, so they need both the Caliburn.Micro packages. However, in these projects I do not need an appbootstrapper of shellview.Xaml..

Coordinator
Feb 21, 2012 at 1:27 AM

We'll probably remove those in a future release. I'd like to add some basic scaffolding to take the place of that. Thanks for the feedback!

Apr 16, 2012 at 9:03 PM

I wholeheartedly agree with rekna.  The first time I switched over a project from using a local source build to Nuget, it shredded my project - suddenly it was using a different bootstrapper and different ShellView, etc.  I had no idea what was going on.  (I had my ShellView in a different place than CM assumed, so it added its own)

If there is a way for a Nuget package to install a project template, that would eliminate the whole issue I think.