-
Notifications
You must be signed in to change notification settings - Fork 225
Port to 2.0.1: TagHelper error: A local or parameter named '__model' cannot be declared in this scope because that name is used in an enclosing local scope to define a local or parameter #1618
Comments
Will complete this work when we have 2.0.1 infrastructure in place. |
Estimated date for release? This is a show stopper for me on upgrading to 2.0. |
@bdominguez we plan to release this in mid-September. Hard to pin down an exact date. However, we'll have pre-release builds of the patch before then, and we'll share details about that once the builds are ready. |
@Eilon thanks. |
This has stopped 6 months of work dead at the last step. |
For folks running into this, can you show what code you have in your |
The __model errors happen on the lines and only errors on publish to Azure (it builds fine) <label asp-for="Password" class="col-md-2 control-label"></label>
<span asp-validation-for="Password" class="text-danger"></span>
<label asp-for="ConfirmPassword" class="col-md-3 control-label"></label>
<span asp-validation-for="ConfirmPassword" class="text-danger"></span>
<span asp-validation-for="Terms" class="text-danger"></span>
|
@Gaelmart thanks. @NTaylorMullen - any idea if there's a workaround that could be used for this? |
@Gaelmart one workaround you could do would be to throw all that TagHelper code that utilizes |
@NTaylorMullen ah that's probably a pretty good workaround that should work in most cases, though it's of course a bit messy. |
This patch bug is approved for the 2.0.x patch. Please send a PR to the |
@ajaybhargavb - I reassigned this to you because @NTaylorMullen is still out. |
888e6bf on branch |
Please may I ask how can we get the fix? |
@rajsingh216 Update to version 2.0.1 once it’s released… |
@Eilon In response to this comment, is there any update on when 2.0.3 is going to be released? I heard you had some release infrastructure problems which are resolved now, so do you have any date you can share? My team is getting a bit anxious since we are still holding off the upgrade because of this. |
@poke we unfortunately still have some infrastructure issues, but we are working right now on getting a preview build of 2.0.3 that people can try out. We don't have an exact date to share on the final release of 2.0.3 just yet. |
@Eilon A preview release would work just fine for me! Anything to allow me to move to 2.0 is great! Thanks for the update and good luck with your infrastructure :) |
@poke thanks, we're working through it! I will update all patch issues with download details when we have a build available to test. |
@Eilon any news on this? I had to jump through some hoops to successfully upgrade to 2.0 as a result of this, but its not sustainable. |
@stefan505 we're working on this right now. It's a bit complicated due to some infrastructure issues but it's a high priority for us. |
Hi, we have a public test feed that you can use to try out the ASP.NET/EF Core 2.0.3 patch! To try out the pre-release patch, please refer to the following guide:
We are looking for feedback on this patch. We'd like to know if you have any issues with this patch by updating your apps and libraries to the latest packages and seeing if it fixes the issues you've had, or if it introduces any new issues. If you have any issues or questions, please reply on this issue to let us know as soon as possible. Thanks, |
Port this fix to 2.0.1: #1614
The text was updated successfully, but these errors were encountered: