Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Attempt to fix VS2022 build errors in CI/CD #84

Merged
merged 1 commit into from
Aug 25, 2022
Merged

Attempt to fix VS2022 build errors in CI/CD #84

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions VS_Meadow_Extension/VS_Meadow_Extension.2022/VS_Meadow_Extension.2022.csproj
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -120,7 +120,7 @@
<PackageReference Include="Microsoft.VisualStudio.Utilities" Version="15.0.0.0" />
<PackageReference Include="Microsoft.VisualStudio.Validation" Version="15.3.0.0" />
<PackageReference Include="Microsoft.VSSDK.BuildTools">
<Version>17.1.4057</Version>
<Version>17.2.2198</Version>
<IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
<PrivateAssets>all</PrivateAssets>
</PackageReference>
Expand Down Expand Up @@ -224,10 +224,10 @@
<Import Project="..\VS_Meadow_Extension.Shared\VS_Win_Meadow_Extension.Shared.projitems" Label="Shared" />
<Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" />
<Import Project="$(VSToolsPath)\VSSDK\Microsoft.VsSDK.targets" Condition="'$(VSToolsPath)' != ''" />
<!-- TODO: This copies the build authoring to a well-known location so that on the machine this project builds on,
the projects created by the 3rd party consumer can open and build. But the real 3rd party consumer will not
have run this step so they won't be able to open their projects.
To ship, the project type author must create an MSI that places these files in a well-known location on the
<!-- TODO: This copies the build authoring to a well-known location so that on the machine this project builds on,
the projects created by the 3rd party consumer can open and build. But the real 3rd party consumer will not
have run this step so they won't be able to open their projects.
To ship, the project type author must create an MSI that places these files in a well-known location on the
customer machine and update the project template to point at that location.-->
<Target Name="AfterBuild">
<ItemGroup>
Expand All @@ -237,4 +237,4 @@
<Copy SourceFiles="@(BuildSystemToCopy)" DestinationFiles="@(BuildSystemToCopy->'$(LocalAppData)\CustomProjectSystems\VS_Meadow_Extension\%(RecursiveDir)%(FileName)%(Extension)')" SkipUnchangedFiles="true" />
<Copy SourceFiles="@(RulesToCopy)" DestinationFiles="@(RulesToCopy->'$(LocalAppData)\CustomProjectSystems\VS_Meadow_Extension\Rules\%(RecursiveDir)%(FileName)%(Extension)')" SkipUnchangedFiles="true" />
</Target>
</Project>
</Project>