Does anyone still use the msi installer for CSLA?
These days I just assume everything of value is in NuGet, and my primary focus with CSLA releases has been NuGet for the past couple years.
I do still maintain the msi installer, but it is kind of a PITA, especially if nobody uses it.
My train of thought is that anyone who wants the samples, source code, and other artifacts can just as easily pull the zip archive that GitHub automatically creates for each CSLA release.
What do you all think? Keep or drop the msi installer project?
Hi,
Drop it. It's just as easy to download using GIT or as a zip file from Github.
Nope. Drop it. So many more important CSLA things on which to spend time...
Ya, I think its safe to do away with the MSI. You could always package samples as NuGet packages too. For source code, it seems like the way to go is push things to SymbolSource.org to push both the PDBs and source code. So those might be worthwhile to look into.
We have been pushing the source to symbolsource for some years now.
Creating a NuGet package for the samples is an interesting idea.
Creating a NuGet package for the samples is an interesting idea.
Oh, haha, I had no idea. That's great to know.
I've now added a work item in GitHub for this possible change
https://github.com/MarimerLLC/csla/issues/376
Comment here or on the issue in GitHub if you have anything to add to the dialog, otherwise I'll probably end up removing the msi installer.
Copyright (c) Marimer LLC