The options that I found were to: Add a reference to PostSharp in Project A. Add dummy code in Project B so that the compiler would detect that the reference is being used. Add a build event to force copy the DLL. I don’t like any of the above solutions. They are hacks in my … Read more
I also would like to be able to add physical folders to a solution, but unfortunately you can’t do so outside a project. The best solution I have found is to add a solution folder with the same name as the physical folder (myFolder in your example), then add files from that physical folder to … Read more
I managed to ‘convert’ the solution file to change the line containing ‘# Visual Studio 2010’ to ‘# Visual Studio 2012’ in the .SLN file.
Resharper supports option layering. You would use it like this: Have one DotSettings file with all your settings in it. For each solution perform these steps: ReSharper -> Manage Options Right-click “Solution ‘Your Solution’ team-shared” Select Add Layer -> Open Settings File Choose the central DotSettings file This would create a DotSettings file for each … Read more
The .sln file indicates the intended version as one of the early lines – for example: Microsoft Visual Studio Solution File, Format Version 12.00 # Visual Studio 2013 or: Microsoft Visual Studio Solution File, Format Version 12.00 # Visual Studio 2012 However – it can only make use of this if the default application for … Read more
The MSDN documentation “Migration Guide to the .NET Framework 4.5” and “How to Configure an App to Support .NET Framework 4 or 4.5” only discusses modifying projects. There’s no details on applying changes to the entire solution at once, nor have I seen a function in VS that supports it. However, there’s a (well-rated) extension … Read more
I find some missing information in the other answers (at least for people who come from other IDEs like, say, Eclipse) . To say that a solution is a container for projects is only part of the thing. The conceptual feature of a VS project (what determines its ‘granularity’) is that one project produces one … Read more
MsBuild.exe [Path to your solution(*.sln)] /t:Build /p:Configuration=Release /p:TargetFrameworkVersion=v4.0
I have a similar situation with external and internal package sources with projects referenced in more than one solution. I just got this working with one of our code bases today and it seems to be working with the developer workstations and our build server. The below process has this scenario in mind (although it … Read more