We split out all region specific settings into thier own config file. Under the root of the web app we create a config folder and place the region specific settings there. So whatever files are living under the root of config will get picked up. our web.config looks something like: . . . <appSettings configSource=”config\appSettings.config”/> … Read more
First off, with 11k question views at the time of this writing, I’m a little surprised by the lack of answers and with all due respect, the quality of the answers, given a fairly straightforward question. So, now that I’ve vented a little bit, I’d like to address this question(s) because I think that it … Read more
I have accepted Alastair Maw’s answer, as it was his suggestion and links that led me to a workable solution, but I am posting here some details of exactly what I did, for anyone else who may be trying to achieve something similar. As a reminder, in its simplest form my application comprises three assemblies: … Read more
Overrides is the more normal qualifier. If the child class redefines a base class function in this way, then regardless of how a child object is referenced (using either a base class or a child class reference) it is the child function that is called. On the other hand, if the child class function Shadows … Read more
While you are in debug mode within the catch {…} block open up the “QuickWatch” window (ctrl+alt+q) and paste in there: ((System.Data.Entity.Validation.DbEntityValidationException)ex).EntityValidationErrors This will allow you to drill down into the ValidationErrors tree. It’s the easiest way I’ve found to get instant insight into these errors. For Visual 2012+ users who care only about the … Read more
Have you tried to delete the Your_Solution_FileName.suo file? The .suo file should be in the same folder as your .sln file, or in the .vs folder for newer versions of Visual Studio. The .vs folder might be hidden. Update for Visual Studio 2017 In VS 2017 the .suo files are located in a different folder: … Read more
IHttpContextAccessor is no longer wired up by default, you have to register it yourself services.TryAddSingleton<IHttpContextAccessor, HttpContextAccessor>();
As mentioned in the question’s comments, differing .NET Framework versions between the projects can cause this. Check your new project’s properties to ensure that a different default version isn’t being used.
eta: There’s a killer article on this stuff by SO’s own @Nick Craver that you should read While the other responses say this, they don’t make it explicit, so I will…. On VS2013.2, to actually trigger the emission of the cited information, you need to not read the message, which says: C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets(1697,5): warning … Read more
Did you try GetUserNameEx(NameDisplay,…)?