You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we can run WPF projects in VS2015 thanks to some MSBuild tips from the Roslyn team.
However, there are some issues when it comes to using Alive on WPF projects in Visual Studio 2013. The gory details can be found at dotnet/roslyn/issues/2779.
We have a couple workarounds in mind. First of all, all users wishing to use Alive on VS2013 must install the Visual Studio 2015 Build Tools via the following.
Hopefully we can figure out proper use of pkgdef to provide binding redirects telling VS to use the 2015 build tools.
Alternatively, we can automatically modify devenv.exe.config with the proper redirects. I'd rather not do this, but it has worked in our tests and allows Alive to function on WPF projects.
We'll close this issue when we've made a decision.
The text was updated successfully, but these errors were encountered:
Currently we can run WPF projects in VS2015 thanks to some MSBuild tips from the Roslyn team.
However, there are some issues when it comes to using Alive on WPF projects in Visual Studio 2013. The gory details can be found at dotnet/roslyn/issues/2779.
We have a couple workarounds in mind. First of all, all users wishing to use Alive on VS2013 must install the Visual Studio 2015 Build Tools via the following.
Now we have two options:
pkgdef
to provide binding redirects telling VS to use the 2015 build tools.devenv.exe.config
with the proper redirects. I'd rather not do this, but it has worked in our tests and allows Alive to function on WPF projects.We'll close this issue when we've made a decision.
The text was updated successfully, but these errors were encountered: