-
Notifications
You must be signed in to change notification settings - Fork 48
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
Add "-vsi" parameter to Generate-R4MVC command #145
Comments
Accidentally clicked on the close button, sorry. Reopening. |
I wanted to share my workaround build target for anyone else who stumbles on this.
<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 "$(ProjectPath)" -vsi 2" />
</Target> |
+1 to this, is very much needed with the fragmentation of dotnet versions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 commandGenerate-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.The text was updated successfully, but these errors were encountered: