-
Notifications
You must be signed in to change notification settings - Fork 223
Commit
- Fixed comment type in BuildHelper\dotnetmf.proj - Upgraded VS integration projects to use VS14 - Fixed setenv_base.cmd to allow building VS2012 VSIX package
- Loading branch information
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,7 @@ | ||
<?xml version="1.0" encoding="utf-8"?> | ||
<Project ToolsVersion="12.0" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003"> | ||
<PropertyGroup> | ||
<MinimumVisualStudioVersion>12.0</MinimumVisualStudioVersion> | ||
<MinimumVisualStudioVersion>14.0</MinimumVisualStudioVersion> | ||
<VisualStudioVersion Condition="'$(VisualStudioVersion)' == ''">11.0</VisualStudioVersion> | ||
This comment has been minimized.
Sorry, something went wrong.
smaillet-ms
Author
Member
|
||
<VSToolsPath Condition="'$(VSToolsPath)' == ''">$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v$(VisualStudioVersion)</VSToolsPath> | ||
<NetMFTemplateName>MFWindowApplication</NetMFTemplateName> | ||
|
2 comments
on commit ae0f29a
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Re: BuildEnv.props - starting with VS14, Microsoft.Build.Tasks.v12.0.dll
was renamed to Microsoft.Build.Tasks.Core.dll
(same in tools/Targets/Microsoft.SPOT.Support.Settings)
$(MSBuildToolsPath) must be pointing to v12.0 to get it build this way, doesn't it?
EDIT: I see, that's because all project files still have ToolsVersion="12.0"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, the reason for that was not requiring VS14 but allowing it, however since then the VS team launched the "Community Edition" making the distinction a bit of a moot point.
Why is this being removed? This was set to allow the configuration to follow the FLAVOR_WIN setting automatically if it was set.