Skip to content

Conversation

@jonpryor
Copy link
Contributor

Some internal workflows require the Xamarin.Android.Sdk.json file in
order to use the generated .vsix.

Copy the generated Xamarin.Android.Sdk.json file into the
directory that $(VsixPath) uses

Some internal workflows require the `Xamarin.Android.Sdk.json` file in
order to use the generated `.vsix`.

Copy the generated `Xamarin.Android.Sdk.json` file into the
directory that `$(VsixPath)` uses
@jonpryor
Copy link
Contributor Author

@victorgarciaaprea: Are there any constraints/requirements on the Xamarin.Android.Sdk.json filename? Does it need to be exactly that, or does it instead need to match the basename of the generated .vsix?

@victorgarciaaprea
Copy link

It needs to be Xamarin.Android.Sdk.json which is what the current build definition we are using to generate .vsman files is expecting. This looks good!

@victorgarciaaprea victorgarciaaprea merged commit 51ff41b into dotnet:master Aug 16, 2017
jonpryor added a commit that referenced this pull request Aug 16, 2017
Some internal workflows require the `Xamarin.Android.Sdk.json` file in
order to use the generated `.vsix`.

Copy the generated `Xamarin.Android.Sdk.json` file into the
directory that `$(VsixPath)` uses
@github-actions github-actions bot locked and limited conversation to collaborators Feb 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants