Add Support For .exe Packages

[benvillalobos]

During development of dotnet/msbuild#5626, we ran into issues trying to publish an .exe package.

Our workaround consisted of setting the following:

<TargetVsixContainerName>Microsoft.Build.UnGAC.exe</TargetVsixContainerName>

To avoid a .vsix being published.

[garath]

@benvillalobos I'm not sure what you're looking for here. Is there something you need from Arcade?

[rainersigwald]

@garath Yes. Arcade makes a bunch of assumptions in its Visual Studio component authoring process that aren't valid in all circumstances--specifically, it assumes that every VS component is a VSIX container, but that's not always true. We had to spackle over a bunch of stuff to get the correct package build. It would be preferable if it was just supported by Arcade.

I'm still trying to understand what this issue is asking for. The link for what the workaround was doesn't seem to be working.

It mentions publishing, do you mean publishing to the dotnetcli storage account for later consumption?

[rainersigwald]

No, this is entirely about building non-VSIX packages. Publishing worked fine.

Current workarounds are

https://github.com/dotnet/msbuild/blob/e89501e67e07fe474a70153e5df3766d27db0085/src/Package/Microsoft.Build.UnGAC/Microsoft.Build.UnGAC.csproj#L7-L8

https://github.com/dotnet/msbuild/blob/e89501e67e07fe474a70153e5df3766d27db0085/src/Package/Microsoft.Build.UnGAC/Microsoft.Build.UnGAC.csproj#L13-L17

No, this is entirely about building non-VSIX packages.

Thanks! That makes sense. I'm showing my bias when I see publishing mentioned 😄