Tooling: MVC Scaffolding does not work if you have configSource on web.config

[regisbsb]

Following this stack-overflow post that up to today still gets upvotes because the issue is not fixed (http://stackoverflow.com/questions/23910162/scaffolding-controller-doesnt-work-with-visual-studio-2013-update-2/26246534#26246534) may I ask you to investigate why the scaffolding does not work when appSettings or configSettings have configSource attributes on them?

Thanks

[sayedihashimi]

TFS:149354

I've added it to our TFS bug tracker, will reply back here soon.

[regisbsb]

Cool, cheers

[regisbsb]

@sayedihashimi any news?

[p770820]

Is it fixed? It still happened. I use VS2015, ASP.NET MVC 5.2, EF6.1。

[regisbsb]

@sayedihashimi bump

[crmckenzie]

+1

[regisbsb]

@sayedihashimi still no news?

[dmitry-osin]

Ahaha, nice. I still have this bug =)

[micahosborne]

+1

[annerajb]

Any update on this?

[worthy7]

Just discovered this in VS2015, I scaffolded my models, THEN implemented a secretConnection.config file, which is referenced via clearly VS is not following this route.

Simply removing the configSource attribute of fixed this.

[regisbsb]

@sayedihashimi has TFS:149354 being prioritized yet?

[deanilvincent]

What I did was Update the EntityFramework using "Manage Nuget Packages" and click "Entity Framework" on the Installed tab then there's Installed Version of 6.1.3 and below is 6.1.2. I clicked the "Update" and the installed turn to "6.1.2" then I click "Update" once again from 6.1.2 -> 6.1.3 and restart the Visual Studio. I created a controller and all is working so soft. :)

[deanilvincent]

By the way, I'm using the Visual Studio Community with Updates 2.

[regisbsb]

@deanilvincent are you sure you have got configSource pointing to external appConfig for example?

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <connectionStrings configSource="connections.config" />
  <appSettings configSource="appSettings.config" />
</configuration>

[lengluo]

Does anyone know if this problem has been solved? I think it's more clearly when we use configSource to
add appsettings.

[davidarborg]

I found that leaving out the ID field gave this error, once added it worked!

using System;

namespace MvcDemo.Models
{
public class Demo
{
public int ID { get; set; } // mandatory !!
public string First_Field { get; set; }
.
.

[regisbsb]

Guys, guys focus! This bug is not related to version or your code. @deanilvincent and @davidarborg have you got a config source on the app settings and connection string? An hour external file? If not this is not the issue you should be commenting on.

[WasabiFan]

I am also experiencing this error, at this point in Visual Studio 2017 RC. Why hasn't this bug gotten any traction? What's the status internally (@sayedihashimi)?

It would be great to get a fix for this -- having to remove the configSource property every time I want to scaffold something is a pain, and discovering the fix in the first place is tough.

[regisbsb]

Sorry about my french but I think at this moment they just cannot give a flying "effe". It has been a solid 1 year now that this has been reported and no one picks up. Famous failure of the prioritization process of bugs. @WasabiFan

[regisbsb]

@shanselman on failure of software, how bugs go from one version to another after 2 years...

[webtools-bot]

The GitHub Issue Tracker for the aspnet/Tooling repo is being deprecated in favor of Visual Studio's Report a Problem tool.

If this issue is still a problem with the RTW release of Visual Studio 2017, please report a new issue using the Report a Problem tool. While you can still use .NET Core and ASP.NET Preview tools with Visual Studio 2015, Visual Studio 2017 is now the officially supported tool for developing .NET Core and ASP.NET Core projects.

By using the Report a Problem tool (available in both VS 2017 and VS 2015), you can collect detailed information about the problem, and send it to Microsoft with just a few button clicks. See Visual Studio's Talk to Us page for more details.

Please use the discussion topic here for feedback and questions on the deprecation of this issue tracker. Thanks!

[mlorbetske]

Sorry for the long delay here. While I'm closing this issue (since it's been posted on the Developer Community site now https://developercommunity.visualstudio.com/content/problem/39037/mvc-scaffolding-does-not-work-with-external-connec.html, thanks @regisbsb!), I will say that this issue does come up in conversation with some regularity. I don't recall the details offhand, but my understanding from the team is that this is more complicated to accomplish than it appears. @prafullbhosale could you post more detail on what all is involved & some of the challenges that need to be overcome for this to work to the Developer Community post please?