ASP.NET Core RC2?

[Jargon64]

I don't suppose you plan to put together an ASP.NET Core RC2 version of this?

[BrainCrumbz]

Wrong assumption 😺 . We did not switch yet one of our current projects to RC2. As on a single machine you can only have either RC1 or RC2, we were just waiting a little bit to find some time to try the change. And the change will first be made on such starter project.

So I'd say it's only a matter of time. Then again, it seems that by the end of this month RTM should be out ... so one might wonder whether it's better to do the intermediate step or two-in-one. I think we'll go for the intermediate step anyway.

So, please be patient ... or maybe submit a PR ;)

[Jargon64]

@BrainCrumbz Ok, no problem. I was drawn here for the routing middleware as ASP.NET Core RC2 module has broken the URL rewriting for IIS. I was unable to adapt said middleware to RC2 and as a result found a different intermediary workaround.

I have, however, bookmarked this repo as this is one of the few seed projects that has Angular 2.x set up, which I plan to move into in the near future :)

[BrainCrumbz]

We already (?) migrated the client side to Angular 2 RC1, so that is sorted (until next Angular update...). I was not aware of such break, i guess you already checked threads like this on SO. As a rough rule of thumb, I've seen people suggesting to avoid URL rewriting rules in IIS altogether for ASP.NET Core (...actually since ASP.NET 5 I think), basically trying to avoid putting custom directives in web.config at all. For such needs as rewrites, they suggested changing your setup in the various Startup methods.

If you're talking about redirecting for a Single Page Application scenario, where you want to allow deeplinking, and thus you want your server side to redirect not found URLs to home, we struggled with that a little and then we made a custom middleware as well. Yet, nothing to be put in web.config

BTW happy to know that this project might be useful to you in the future!