Add "-vsi" parameter to Generate-R4MVC command

[gpattersonclearwave]

I have multiple instances of VS installed (2017, 2019) and I am experiencing the same issue as described in #132 and it looks like the resolution is to specify the visual studio instance being used by the underlying application with the -vsi parameter. The PowerShell wrapper command Generate-R4MVC does not expose a parameter to pass this through. This forces me to do some jumping around to get the tool to generate files correctly for my .Net Core 3 projects. Please add an optional pass-through for this parameter, defaulting to the current behavior when nothing is specified.

[gpattersonclearwave]

Accidentally clicked on the close button, sorry. Reopening.

[gpattersonclearwave]

I wanted to share my workaround build target for anyone else who stumbles on this.

1. Add GeneratePathProperty="true" to the R4Mvc.Tools package reference
2. Get the list of instances by running R4Mvc.Tools.exe vsinstances, then append the build task to your csproj:

<Target Name="GenerateR4Mvc" BeforeTargets="Build">
    <PropertyGroup>
      <R4MvcToolsExe>$(PkgR4Mvc_Tools)\tools\R4Mvc.Tools.exe</R4MvcToolsExe>
    </PropertyGroup>
    <Message Text="Running R4Mvc" Importance="high" />
    <Exec Command="$(R4MvcToolsExe) generate -p &quot;$(ProjectPath)&quot; -vsi 2" />
  </Target>

[valeriob]

+1 to this, is very much needed with the fragmentation of dotnet versions.