Skip to content

Add global.json to force sdk 6.0.100 #7656

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.

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

Merged
merged 2 commits into from
Jan 15, 2022
Merged

Conversation

gave92
Copy link
Member

@gave92 gave92 commented Jan 14, 2022

Resolved / Related Issues
Items resolved / related issues by this PR.

  • Expected to close #7592

Details of Changes
Add details of changes here.

  • Add global.json to force sdk 6.0.100

This change should force the Store to build the app using sdk 6.0.100 like CI does. This apparently is mandatory or fulltrust process will crash (at least on windows 10).

NOTE: adding this file to the repo will cause building the app to fail unless the exact version of the sdk is installed. This is annoying for contributors, if possible I'd only use it when submitting a new version to the Store.

@yaira2
Copy link
Member

yaira2 commented Jan 14, 2022

@gave92 the store recompiles the app on their servers, will this help for that?

@gave92
Copy link
Member Author

gave92 commented Jan 14, 2022

I'm hoping it does, I have no experience with the Store. Is it possible to test Store version before publishing it to everyone?

@yaira2 yaira2 merged commit 048e37d into files-community:main Jan 15, 2022
@yaira2
Copy link
Member

yaira2 commented Jan 15, 2022

@gave92 I'll test it out and if it doesn't work, we can revert the change.

yaira2 added a commit that referenced this pull request Jan 16, 2022
yaira2 added a commit that referenced this pull request Jan 16, 2022
@yaira2
Copy link
Member

yaira2 commented Jan 16, 2022

@gave92 gave92 deleted the globals branch January 16, 2022 10:10
@gave92
Copy link
Member Author

gave92 commented Jan 16, 2022

Store pipeline is getting the wrong sdk version in "UseDotNet" step. Sideload release was perfectly fine.

@gave92
Copy link
Member Author

gave92 commented Jan 16, 2022

@yaichenbaum what .yml configuration file is used for store release? You need to do the same change that was done in #7422

@yaira2
Copy link
Member

yaira2 commented Jan 16, 2022

@gave92 it's the release pipeline so it was already done 🤔

@gave92
Copy link
Member Author

gave92 commented Jan 16, 2022

Gah found it

@yaira2
Copy link
Member

yaira2 commented Jan 16, 2022

Gah found it

Ha! It was changed but only for the sideload release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants