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.

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

[wasm][debugger] Shipping internal package for webcil #99380

Merged
merged 5 commits into from
Mar 11, 2024

Conversation

thaystg
Copy link
Member

@thaystg thaystg commented Mar 6, 2024

Shipping internally webcil package that will be consumed from an external repo.

@thaystg
Copy link
Member Author

thaystg commented Mar 6, 2024

@akoeplinger is this enough to ship the package internally as we do for Microsoft.NETCore.BrowserDebugHost.Transport?

@ghost
Copy link

ghost commented Mar 6, 2024

Tagging subscribers to this area: @thaystg
See info in area-owners.md if you want to be subscribed.

Issue Details

Shipping internally webcil package that will be consumed from an external repo.

Author: thaystg
Assignees: thaystg
Labels:

area-Build-mono, area-Debugger-mono

Milestone: -

@@ -9,7 +9,7 @@
<ProjectReference Include="Microsoft.NET.Runtime.WebAssembly.Sdk\Microsoft.NET.Runtime.WebAssembly.Sdk.pkgproj" />
<ProjectReference Include="..\wasm\templates\Microsoft.NET.Runtime.WebAssembly.Templates.csproj" />
<ProjectReference Include="Microsoft.NET.Sdk.WebAssembly.Pack\Microsoft.NET.Sdk.WebAssembly.Pack.pkgproj" />

<ProjectReference Include="Microsoft.NET.WebAssembly.Webcil\Microsoft.NET.WebAssembly.Webcil.pkgproj" />
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This pkgproj doesn't exist, you'd need to create it

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, I forgot to add the file!

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@thaystg if all you need is a nuget package then you don't need the .pkgproj (which is kinda deprecated), you can just set <IsPackable>true</IsPackable> in the .csproj.

@@ -9,8 +9,7 @@
<Serviceable>true</Serviceable>
<AllowUnsafeBlocks>true</AllowUnsafeBlocks>
<IsShipping>true</IsShipping>
<!-- this assembly should not produce a public package, rather it's meant to be shipped by the
WasmAppBuilder task and the BrowserDebugProxy -->
<!-- this assembly should produce a non-shipping package, because it will be used by BrowserDebugProxy -->
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WasmAppBuilder still uses this though?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes.

@akoeplinger
Copy link
Member

akoeplinger commented Mar 7, 2024

I'm not sure what the goal here is and what exactly you mean with "internal". The distinction we have is Shipping (i.e. to nuget.org) or Non-Shipping (to some dnceng-feeds) but both of these still mean the package is publicly available.

@thaystg thaystg requested a review from lewing as a code owner March 7, 2024 12:12
@thaystg
Copy link
Member Author

thaystg commented Mar 7, 2024

I'm not sure what the goal here is and what exactly you mean with "internal". The distinction we have is Shipping (i.e. to nuget.org) or Non-Shipping (to some dnceng-feeds) but both of these still mean the package is publicly available.

The goal is to use it in another repo. It's okay to be in dnceng-feeds. Thanks for the explanation.

@thaystg thaystg merged commit d98a887 into dotnet:main Mar 11, 2024
33 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Apr 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants