TLDR: Yes NuGet uses a hierarchical application of package sources starting with the NuGet.config at the level of your Windows User Profile and then applying more and more granular configuration starting at the root of the file path that contains your solution, finally ending with the directory containing your solution file. So here’s what I’ve … Read more
1 After editing applicationhost.config file (located in the IISExpress folder in your documents), your site bindings should look like below: <bindings> <binding protocol=”http” bindingInformation=”*:8080:*” /> </bindings> Bindings consist of three parts. Firstly an IP address or list, or as in this case, a wildcard. Secondly the port number, and thirdly a hostname, or list, or … Read more
The answers provided by Dai Bok and emalamisura work fine as long as you use Visual Studio 2012. For VS 2013 this fails as well. In order to make this work with all versions of Visual Studio you should: Open the project file (.csproj) of the project failing to load Search for <Import Project=”$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v10.0\Web\Microsoft.Web.Publishing.targets” /> … Read more
Sometimes it’s enough to simply delete the “.v12.suo” file and try to open the solution again. Helped me many times when VS2013 was freezing on loading a project.
This may be a possible answer for the problem. Some from the answer: Check which files were changed (why and how) after update from a source control engine Review the list of extensions and plugins. Try to disable all or some of them Close Visual Studio and kill all the development processes: devenv, mspdbsrv, vcpkgsrv, … Read more
Log file from Visual Studio is only supported for C++ projects. You just have to work with the output window for others. See this similar thread: VS2010: minimal build log in output and detailed log in log file And in case you happen to do this for a C++ project, the file is at: … … Read more
If you use Visual Studio 2010, you can use the free Visual Studio 2010 Productivity Power Tools from Microsoft to achieve this.
Install Nuget. Right click on the solution and select “Enable NuGet Package Restore”. In Visual Studio 2013 and later, select “Restore NuGet Packages” instead. Click Ok on the warning. Close and re-open the solution. Should now be hunky-dory.
You can change the default namespace: -> Project -> XXX Properties… On Application tab: Default namespace Other than that: Ctrl-H Find: WindowsFormsApplication16 Replace: MyName
Your point #3 (Add references to various .dll files/other projects <– this is the missing part) really contains two different issues: (1) add references to various dll files, and (2) add references to other projects in the same solution. Number (2) here has gotten some added support as of NuGet 2.5. You can add an … Read more