I'm reading a book about MVC ASP.NET, there are some hidden project setup that you can only modify by 'unload'
the whole first(then all the structure gone), then after clicking 'edit'
, change the xml tag value.
That reminds me to ask: why we need to unload the project before we modify the config file? Can anybody tell me the meaning of unloading project?
Why not just open the folder location and change by Notepad?
Right click on the project folder and click Reload project.
In Solution Explorer, select the projects you want to load (press Ctrl while clicking to select more than one project), and then right-click on the project and choose Reload Project. Visual Studio will remember which projects are loaded the next time you open the solution locally.
A project is contained within a solution. Despite its name, a solution isn't an "answer". It's simply a container for one or more related projects, along with build information, Visual Studio window settings, and any miscellaneous files that aren't associated with a particular project.
In Solution Explorer, right-click the project and select Unload Project.
It can be useful to unload a project from a solution while resolving circular dependencies between projects or conflicts with different versions of the .NET framework between projects.
It is considerably more difficult and error-prone to directly edit the configuration files with Notepad.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With