Hi -
Excited about your new Ang+Core support! Thanks.
So I downloaded some new projects a few hours ago and decided to bleeding edge test them on Mac Sierra with latest and greatest npm+node+yarn+ng+dotnet+typescript+vscode. So far so good. I did run up against a few simple issues (as a heads up):
ng server only recognizes the --live-reload-client nuget package incompatibilities for netcoreapi1.1 like Microsoft.Composition vs. System.Composition etc...
I solved both, but noticed you (almost concurrently) did the same in the github template. Hence, my issue about long term maintenace.
We have templated projects that are hard to sync with your template development and hot fixes. I can obviously fork/sync and monitor your template repo and manually update our projects. Is there a better (painless) way you recommend? Diff tools are interesting but since we have templated namespaces....
Regards, P
5 Answer(s)
-
0
Hi,
Following link can help you. <a class="postlink" href="https://github.com/aspnetzero/aspnet-zero/issues/96#issuecomment-186843738">https://github.com/aspnetzero/aspnet-ze ... -186843738</a>
-
0
Thanks. Hits the spot!
P
-
0
I also want to keep my application up to date, and I'm considering this upgrade process.
- Fork aspnet-zero-core
- Revoke access to teams.
- Add my files.
I'd be stuck with the namespace for all template files: MyCompanyName.AbpZeroTemplate But most of my files I will keep in separate projects (modules) that uses my namespace.
Because I revoked team access, then this fork shouldn't be able to be accessed by other volosoft customers, correct? So I shouldn't appear on this list (maybe?): <a class="postlink" href="https://github.com/aspnetzero/aspnet-zero-core/network/members">https://github.com/aspnetzero/aspnet-ze ... rk/members</a> And this should be inaccessible (except to me): <a class="postlink" href="https://github.com/saasygreene/aspnet-zero-core">https://github.com/saasygreene/aspnet-zero-core</a>
Is this all correct? Anything I haven't considered?
If it affects anything: I am using .Net Framework, not .NET Core
-
0
Hi @SaaSyGreene,
As far as I know, your assumptions are right. You can also consider downoading the new version with your project's name and do it on a local or private git repository.
-
0
Keep in mind that the github code does not have the renaming applied to the template, so all of the namespaces, and most of the file names will not match your code, making mergers difficult to manage.
We have found that the easiest way to stay up to date is to download the latest release, replace our existing source folder, and then comb through the git changes to isolate any overrides to our customization.
For our Domain and Application layers, we have created 2 new modules so that the majority of our code won't be affected by the merger.
It's not the most ideal process, but it's been working well so far.
