[release/6.0.1xx-rc2] BlazorWasm: Fix including the target assembly

[radical]

Use $(IntermediateAssembly) when gathering files for wasm build.

Fixes dotnet/runtime#59255 .

[SteveSandersonMS]

Makes sense based on what I saw before. Will this make it able to pick up DllImport from ProjectReferences too (if it didn’t already)?

[radical]

Will this make it able to pick up DllImport from ProjectReferences too (if it didn’t already)?

Can you elaborate on this?

[SteveSandersonMS]

I just wanted to check that the issue that prevented it seeing your main assembly didn’t also prevent it from seeing the assemblies of other projects in your solution.

We know the feature works for PackageReference dependencies, but does it work for ProjectReference dependencies? Has that been tried out?

Hope that makes sense!

[radical]

I just wanted to check that the issue that prevented it seeing your main assembly didn’t also prevent it from seeing the assemblies of other projects in your solution.

Yes, dllimports in referenced projects would get scanned for pinvokes during the native build. Currently, the native library won't get automatically included in the app project though. IOW, you would need an explicit <NativeFileReference Include="/path/to/native/lib" /> in the app project.
But we are trying to figure out how the experience could be different.

[SteveSandersonMS]

IOW, you would need an explicit <NativeFileReference Include="/path/to/native/lib" /> in the app project.

Package authors could already fix that themselves by including some MSBuild in their package that adds a <NativeFileReference> itemgroup entry to any project that consumes the package. Maybe we could make that easier for them one day, but for 6.0, I think we already have the necessary capabilities.

[lewing]

@marcpopMSFT what is the process to get this in rc2 now?