Add NuGet Packages Folder to Solution File?
You may be interested in reading this NuGet doc: Using NuGet without committing packages to source control
You may be interested in reading this NuGet doc: Using NuGet without committing packages to source control
Open the pending changes window. You can find there a toolbar button that filters on the current solution.
See .NET 4.0 MSBuild API introduction for an example using the .NET 4.0 MSBuild API: List<ILogger> loggers = new List<ILogger>(); loggers.Add(new ConsoleLogger()); var projectCollection = new ProjectCollection(); projectCollection.RegisterLoggers(loggers); var project = projectCollection.LoadProject(buildFileUri); // Needs a reference to System.Xml try { project.Build(); } finally { projectCollection.UnregisterAllLoggers(); } A simpler example: var project = new Project(buildFileUri, null, … Read more
I guess I will have to definitively crush your dream. Sorry. It has been a decision by Microsoft to remove this from the default view to reduce the ‘clutter’. However, your ‘Show All Files’ setting will persist when you save your project. So if you show all files once and then save, then it will … Read more
Yes, your hunch was right. It does mean that the project has its Build option ticked to build under the build configuration. I just tested this by opening the solution in one instance of Visual Studio and the .sln file in the text editor (open with) of another Visual Studio instance. If you change the … Read more
Just use the environment variable in the relevant field: OutputDirectory=”$(MyEnvVariableName)\Bin” One trick is that you need to restart the Visual Studio IDE each time you change the variable. There is an MSDN article precisely about this: How to: Use Environment Variables in a Build
This information is stored in the solution user options file (.suo) which you can find in the same directory as the solution file. As the name implies this is user specific information which means sharing this across the team will be difficult because then everyone will need to live with the same options and store … Read more
This is one of those questions that unfortunately doesn’t have a single answer – it depends. The easiest solution is always to have a single repository. This avoids many of the problems of managing multiple repositories with different versions. But this only really works if you have a single version of everything; it’s almost impossible … Read more
There’s easy way to do this: in web project’s properties F4 (NOT right click-> properties) set “always start when debugging” to false
If you have ReSharper installed, on the settings for the directory (F4), set Namespace Provider to false.