-
Notifications
You must be signed in to change notification settings - Fork 53
Converting the project to cspoj #11
Comments
I totally agree. My idea was to do that once VS2015 tools come out of preview, or when VS2017 goes RTM. Do you need it sooner? |
Not really. The reason being I want to project reference the ServiceFabric.PubSubActors and ServiceFabric.PubSubActors.Interfaces projects from the demo project so I can step through it. But looks like nuget manager is not finding it because they are xproj. Let me know if there is another work around. Thanks |
Ignore about referencing the libraries. I got it work. |
For any other readers that want to debug, you don't need a project reference. Symbols are published here: http://www.symbolsource.org/Public/Home/VisualStudio Option two would be to install .net core on your machine, compile the project to get the PDB's and manually load symbols using the Debug->Windows ->Modules window in Visual Studio. |
@loekd If I need to modify some code in the package(ServiceFabric.PubSubActors) itself, so I think I need to project reference the package code from the demo project, so I can step through the modified code. So not sure if I am setting up my environment correctly for this project. |
Changing the code is a lot easier with project references indeed. |
@alltej I've converted to VS2017 & csproj files. |
thanks for converting it! also thanks for accepting my PR :) |
Since the xproj and project.sjon are going away for .NET core, it might make sense to convert the project to csproj. What you think?
The text was updated successfully, but these errors were encountered: