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
I am looking at porting our complete product (+150 projects) to .NET Standard but I am encountering a problem between .NET Standard libs and our big WebForms Website (so not a web application but the one without a csproj).
I have ported some classic Class Libraries to .NET Standard Class Libraries and it works suprisingly well except the F12 Go to Definition is not working between them. When I am inside my Website project and I press F12 on type that lives in a .NET Standard lib I will get the "metadata" version. So it is not directly jumping into my source code, which is kind of a dealbreaker because you cannot simply edit the source code. The workaround is to navigate to it yourself (CTRL + T) but that is not really an option imo.
This issue is really holding me back to port our large code base to .NET Standard so my hope is that this will be on the backlog
The text was updated successfully, but these errors were encountered:
I am looking at porting our complete product (+150 projects) to .NET Standard but I am encountering a problem between .NET Standard libs and our big WebForms Website (so not a web application but the one without a
csproj
).I have ported some classic Class Libraries to .NET Standard Class Libraries and it works suprisingly well except the
F12 Go to Definition
is not working between them. When I am inside my Website project and I pressF12
on type that lives in a .NET Standard lib I will get the "metadata" version. So it is not directly jumping into my source code, which is kind of a dealbreaker because you cannot simply edit the source code. The workaround is to navigate to it yourself (CTRL + T
) but that is not really an option imo.This issue is really holding me back to port our large code base to .NET Standard so my hope is that this will be on the backlog
The text was updated successfully, but these errors were encountered: