csproj

问题 In my Windows CE app, I have been trying to change all project references from "Any CPU" (or "AnyCPU") to "x86" To do so, I've hand-edited the .csproj file (Project > Properties... only has "Any CPU" available as an option, no "x86" (or anything else). Now that I've dont that, though, I get, " The OutputPath property is not set for this project. Please check to make sure that you have specified a valid Configuration/Platform combination. Configuration='Debug' Platform='AnyCPU' " Where the

问题 I've downloaded a framework with samples in .csproj project format. How can I open them in MonoDevelop? I'm interested in using some classes in that framework. It has a folder structure like: Accord.Statistics.Models and a main folder Accord with a subfolder Statistics with a subfolder Models with a file ModelFoo.cs I want to use that file (that begin with namespace Accord.Statistics.Models ) in a MonoDevelop Solution under Ubuntu. If I copy the folder or single files inside my new Solution I

问题 I upgraded a netcore1.1 project to the new VS2017/csproj. In my test projects only, it added: <PropertyGroup> <GenerateRuntimeConfigurationFiles>true</GenerateRuntimeConfigurationFiles> </PropertyGroup> I did some digging to discover that it generates these files in the bin directory: ProjectName.Tests.runtimeconfig.json ProjectName.Tests.runtimeconfig.dev.json What is this setting and these files, and why do I need them? Why were they only generated for my test projects? 回答1: These are

问题 (Question subtitle: Are resources not supported in .netstandard 1.3 or is my project file just messed up?) I just created an example portable class library in Visual Studio 2015 Update 3 and added a sample resource file. Initially, the file project.json looks like this: { "supports": { "net46.app": {}, "uwp.10.0.app": {}, "dnxcore50.app": {} }, "dependencies": { "Microsoft.NETCore": "5.0.0", "Microsoft.NETCore.Portable.Compatibility": "1.0.0" }, "frameworks": { "dotnet": { "imports":

问题 (Question subtitle: Are resources not supported in .netstandard 1.3 or is my project file just messed up?) I just created an example portable class library in Visual Studio 2015 Update 3 and added a sample resource file. Initially, the file project.json looks like this: { "supports": { "net46.app": {}, "uwp.10.0.app": {}, "dnxcore50.app": {} }, "dependencies": { "Microsoft.NETCore": "5.0.0", "Microsoft.NETCore.Portable.Compatibility": "1.0.0" }, "frameworks": { "dotnet": { "imports":

问题 I have a code generator tool that I partially own, and now that csproj files can list multiple Target Frameworks in them and building builds all of them, I am trying to figure out how to make an MSBuild Target to do the code generation only once per running the build, no matter how many Target Frameworks are listed, and have the compiling for each of the Target Frameworks wait until the code generation has completed. I currently have it conditional on a specific value of TargetFramework. For

问题 This question already has answers here : How to upgrade csproj files with VS2017 (3 answers) Closed 6 months ago . I have two projects in VS2015 One .NET Core (project.json, xproj) One regular .NET csproj When I open project 1 with VS2017, it nicely migrates to the new csproj format. Project 2 works in VS2017, but I like to convert/migrate/update this csproj to the new project file format to benefit from the new csproj features (multi target, no large file list, readable csproj, NuSpec info

问题 Is it possible to split the information in a .csproj across more than one file? A bit like a project version of the partial class feature. 回答1: You can not have more than one master csproj. But because the underneath wiring of the csproj is done using msbuild you can simply have multiple partial csproj that import each other. The solution file would see the most derived csproj. project1.csproj <Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003"> .... <

问题 Let's imagine I already have a project building .NET 3.5 assembly. Now I want to build this assembly for Silverlight, and moreover, maintain its Silverlight version with minimal efforts further. What is not acceptable: Creating separate project for Silverlight build What is acceptable: Adding custom directives allowing me to target either Silverlight or .NET dependently on e.g. MSBuild properties. Adding special build configurations for Silverlight Adding #ifdef Silverlight / #endif sections

问题 Here's a snippet from my csproj file: <ProjectReference Include="..\program_data\program_data.csproj" Condition="'$(Configuration)'=='Debug'"> <Project>{4F9034E0-B8E3-448E-8794-CF9B9A5E7D46}</Project> <Name>program_data</Name> </ProjectReference> What I'd like to do is include program_data.dll for multiple build configurations, for example, both Release and Debug. I tried doing the following Condition="'$(Configuration)'=='Debug' || '$(Configuration)'=='Release'" but Visual Studio chokes on