Hi,
I am looking for some strategies as to how to go about integrating changes made between releases of the downloadable template. I have just got the template a couple of days ago (so lets call that version 1.10).
As my application will ultimately be an MPA I want to take out all the SPA stuff and then of course I want to change things, most notably move things around, rename things. However that is where the trouble will start.
If I say pick a change from the upcoming 1.11 release at random: [https://github.com/aspnetzero/aspnet-zero/commit/dd7883e3dd87ff422bc32963dba8d648ed95c0da]). A quick look tells me there are EIGHT file changes and ~250 changes all up.
So now I want to go about folding in those changes to my application, as I see it I would have to:
- Generate a new template download named with the same application name and company name
- Diff 1. against my current code base
- Work out what to change based on 2.
The above sounds like a nightmare to me and very time consuming. I am hoping that I am missing something obvious here and that there is a simple(r) solution to this?
Any comments and suggestions greatly appreciated.
19 Answer(s)
-
0
Thanks Halil. It just confirmed what I thought which is good ;-). Agree updating the template will be onerous and there is no simple fix - was just hoping there was. 8-) I will look at the Git solution proposed as mentioned in that article.
As I have a few days before I really start I was wondering if I could pose the following questions to you:
- Any timeline on splitting the template into SPA / MPA versions (<a class="postlink" href="https://github.com/aspnetzero/aspnet-zero/issues/251">https://github.com/aspnetzero/aspnet-zero/issues/251</a>)
- Any ETA on 1.11 (<a class="postlink" href="https://github.com/aspnetzero/aspnet-zero/milestone/17">https://github.com/aspnetzero/aspnet-zero/milestone/17</a>)
Stating the obvious:
Having 1. means I only have to worry about changes to whichever I am using (Huge saving if all the changes are SPA fixes for instance and I am using MPA). Once the solutions are split then constructs introduced to support both SPA and MPA in the same solution can be dropped. Eg MPA area would no longer be needed. Code in template is simplified as all the scaffolding to support that can be ditched. Routes for SPA, MPA will be the same and so on.
I may as well wait until 1.11 before I start making serious changes irresepective of 1.
-
0
Hi,
It's hard to split into two separated respositories since there are many common code which we don't want to duplicate. But we can enhance project creator to automatically remove SPA if you choice MPA (and vice verse).
Estimated date is 22.07.2016. We hope to release it in that date.
Have a nice day.
-
0
Much appreciated Halil.
- Cool and I see 1. is also slated for 1.11. Much appreciated.
- I realise it is only an estimate and it can change, but it may be worth adding release dates to milestones in GitHub so that there is some idea of when. This would tie into my logical roadmap request as well. ;-)
-
0
I'm not sure to set a date because it will be more problem to change it later :) But OK, we will consider this suggestion for next release.
-
0
Is the ETA for 1.11 still 22 July? I realise there have been a few issues with things breaking of late so you may have been occupied elsewhere. :-)
However I really want to start my new project with the MPA and SPA separation. A deadline is looming for me and I am already worrying about the integration as I have started using 1.10 in the mean time.
-
0
Bump!
-
0
Hi,
It's 26 July actually. We are hardly trying to finish issues for that date :)
-
0
Hi,
Any ETA? I realise it is the 27th here already for almost a full day ;-)
-
0
Hi,
We are sorry for the delay. We need a few more days to close open issues.
-
0
Any update on when ZERO 1.11.1 will be out? Really looking forward to the SPA/MPA template generator (<a class="postlink" href="https://github.com/aspnetzero/aspnet-zero/milestone/20">https://github.com/aspnetzero/aspnet-zero/milestone/20</a>)
-
0
Hi,
We are planning to release in a few days. I know that you are waiting for seperation of MPA and SPA feature but unfortunately it's not going to be in this release as well.
We might do it after this release.
-
0
Hi,
We might do it after this release.
Ummm. Can we get some confirmation that this is going to be the case?
For me the comprehensive split of the MPA / SPA is a big deal as I am sure it will also help clean up a heap of the code in the presentation layer. As the migration path once you are using the template is not straight forward - I don't want to have to go and clean up all the code (to remove the SPA) only to have the template restructured on your end after that. It will make things so much harder for me to integrate new features as they are released.
While I realise it is not easy (even though the code is well structured) to separate SPA / MPA this has been promised early July and we are now heading towards the end of August. :?
-
0
Hi,
You are right. We planned to do it in the past but currently we are focused on mvoing to AspNet Core and Angular2 and it takes most of our time.
In that version it will be seperate from the beginning.
-
0
<cite>ismcagdas: </cite> Hi,
You are right. We planned to do it in the past but currently we are focused on mvoing to AspNet Core and Angular2 and it takes most of our time.
In that version it will be seperate from the beginning.
You have still not answered my question. :) When will it be delivered? Ultimately Core and Angular 2 are not of interest to me at this point. I need MPA and MVC.
-
0
Hi,
We actually didn't set a date for this issue. We are planning to do it after finishing the Core and angular2 version. I assume it will take a few months to deliver this.
-
0
<cite>ismcagdas: </cite> Hi,
We actually didn't set a date for this issue.
Actually you did: #1372
and in fact it was slated for the 1.11 release of ZERO. This is NOT cool guys. :x The least you owe me is an actual delivery date of this functionality. Not something vague. Because I could wait 2 months only to have it pushed again. I see it is now in milestone 2.1 which has no due date. As a commercial customer this is not great that things can move with no actual roadmap, voted set of changes or due dates on milestones.
-
0
Hi,
Sorry, we sometimes changing our milestone items based on changing conditions. But it seems we didn't understand well that this is a critical feature for you. Please continue to discuss this on <a class="postlink" href="https://github.com/aspnetzero/aspnet-zero/issues/251#issuecomment-242288363">https://github.com/aspnetzero/aspnet-ze ... -242288363</a>
Thanks.
