Versioning and releasing multiple assemblies and their NuGet packages
@brianlagunas wrote: I have run into an issue with assembly versions vs. NuGet package versions and dealing with multiple assemblies (versioned differently) within a single package. I am sure this is...
View ArticleVersioning and releasing multiple assemblies and their NuGet packages
@richlander wrote: I read that Prism.Unity is a high-level package that has dependencies on all of the other packages. Presumably, there are changes to the lower-level packages that don't affect...
View ArticleClik here to view.
Versioning and releasing multiple assemblies and their NuGet packages
@brianlagunas wrote: Actually, the dependencies are not the issue. Although, NuGet will not bring down a newer package with an install. For example; if Prism.Unity has a dependency on Prism.WPF v1.0...
View ArticleVersioning and releasing multiple assemblies and their NuGet packages
@csharpfritz wrote: You've really got a confusing block of packages and support verticals there before we even look at the version numbers. Am I understanding correctly that I need to choose a DI...
View ArticleVersioning and releasing multiple assemblies and their NuGet packages
@brianlagunas wrote: Your UI framework is chosen when you open VS and say File -> New. You do need to choose your preferred DI container though. (Unity, SturctureMap, Ninject, etc). This is why we...
View Article