In my case, the gt_strd5.sfproj file contained four references which needed to be updated from 1.5.0 to 1.6.0. I found that after the change, some references in the application's project file continued to reference MSBuild 1.5.0. gt_strd5 C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin\ 2630 gt_strd5 C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin\ 737Įrror MSB4057 The target "CreateManifestResourceNames" does not exist in the project. This error may also appear if some other project is trying toen unloaded or is not included in the solution, and the referencing project does not build using the same or an equivalent Configuration or Platform. Configuration='Debug' P follow a project-to-project reference to this project, this project has belatform='圆4'. Please check to make sure that you have specified a valid combination of Configuration and Platform for this project. Severity Code Description Project File Line Suppression StateĮrror The OutputPath property is not set for project 'gt_strd5.sfproj'. If I run the solution this way, it runs fine on my local Service Fabric cluster.īut when after I use NuGet to update the application's MSBuild to 1.6.0 (so both application and server projects use the same), the following errors occur.
The service uses MSBuild version 1.6.0 (the current "latest"). The application uses MSBuild version 1.5.0. When VS2017 was used to create a stateful solution, producing the standard boilerplate code, the resulting two projects have two different MSBuild versions.
0 kommentar(er)
