csproj

I'm using Visual Studio 2012 RC to work with my C# solution. All my configuration-specific settings are stored within a single .props file which is then included by all my .csproj files. Yet VS insists on putting this right in front of the include: <PropertyGroup Condition="'$(Configuration)|$(Platform)' == 'Debug|AnyCPU'"> <IntermediateOutputPath>C:\Users\xyz\AppData\Local\Temp\vs855E.tmp\Debug\</IntermediateOutputPath> </PropertyGroup> <PropertyGroup Condition="'$(Configuration)|$(Platform)' == 'Release|AnyCPU'"> <IntermediateOutputPath>C:\Users\xyz\AppData\Local\Temp\vs855E.tmp\Release\<

Context : In our application there two separate dlls which are repositories of variables configured for different types of hardware .These dlls has same name and is referenced from our application, Now every time if we wanted to test the different type of hardware we have to copy the relevant dll to the location where application is running. I am looking for a workaround. References : I have seen the following threads , 1) .csproj multiple hint paths for an assembly 2) https://whathecode.wordpress.com/2012/10/07/conditional-project-or-library-reference-in-visual-studio/ Question: Can i declare

The recently-released .NET tooling seem to have support for embedding C# in PDBs , which should improve the experience of stepping into third-party, etc. Running csc /? , I can clearly see the /embed option: "Embed all source files in the PDB." However, there doesn't seem to be any way to specify this in csproj. What's more, there doesn't seem to be any provisions for passing arbitrary switches to the compiler, which I would use to manually pass /embed. Can anyone confirm that I haven't missed anything and that build support for /embed is currently lacking? Is there an issue for this (and if

I have AssemblyInfo.cs file automatically generated during build. Here's part of .csproj file: <PropertyGroup> <Major>2</Major> <Minor>3</Minor> <Build>0</Build> <Revision>0</Revision> </PropertyGroup> <Target Name="BeforeBuild"> <SvnVersion LocalPath="$(MSBuildProjectDirectory)" ToolPath="C:\Program Files\VisualSVN Server\bin"> <Output TaskParameter="Revision" PropertyName="Revision" /> </SvnVersion> <AssemblyInfo CodeLanguage="CS" OutputFile="$(MSBuildProjectDirectory)\Properties\VersionInfo.cs" AssemblyVersion="$(Major).$(Minor).$(Build).$(Revision)" AssemblyFileVersion="$(Major).$(Minor).$

Someone on our team installed StyleCop and since then all of the projects he loaded up and committed to source control refuse to load unless stylecop is installed. I know I can manually edit the .csproj files to get rid of it, but is there an easy way to automatically remove these stylecop parts from the project files so they can be loaded and built on a non-stylecop-infected Visual Studio machine? I disabled StyleCop by adding the following GlobalSettings configuration to the file settings.stylecop in the solution root. <StyleCopSettings Version="4.3"> <GlobalSettings> <BooleanProperty Name=

After upgrading to a csproj to use Visual Studio 2017 and Microsoft.NET.Sdk, my "BeforeBuild" and "AfterBuild" targets are no longer running. My file looks like this: <Project Sdk="Microsoft.NET.Sdk"> <PropertyGroup> <TargetFramework>net46</TargetFramework> </PropertyGroup> <!-- my targets that don't run --> <Target Name="BeforeBuild"> <Message Text="Should run before build" Importance="High" /> </Target> <Target Name="AfterBuild"> <Message Text="Should run after build" Importance="High" /> </Target> </Project> The associated MSBuild git issue recommends not using BeforeBuild/AfterBuild as

I've tried several times to use a similar technique as "conditional references" for conditional content. Content entries in the Visual Studio Project file such as "web.config" I do not want included when I publish the website. I've tried a few things like... <Choose> <When Condition="$(Configuration) != 'Release'"> <ItemGroup> <Content Include="web.config"> <SubType>Designer</SubType> <CopyToOutputDirectory>Always</CopyToOutputDirectory> </Content> </ItemGroup> </When> <Otherwise> <ItemGroup> </ItemGroup> </Otherwise> </Choose> But this doesn't work. Any ideas? Or have you encountered this