Closed jmkelly closed 7 years ago
I have experienced something like this myself when installing multiple NuGet packages in succession.
When I installed them one at a time, trying to build the solution with compile errors and everything in between, it seemed to work as it should.
My guess is that VS2017 does not flush its in-mem project model to the .csproj file often enough, resulting in somehow "overwriting" what would become the <PackageReference>
element in the .csproj file had it been saved.
Did you by any change first Install-Package Rebus -pre
and then immediately after Install-Package Rebus.SqlServer -pre
?
I did it via the GUI ticking include pre release, but pretty sure I did install in the order you mentioned.
On Thu, 13 Apr 2017 at 5:37 am, Mogens Heller Grabe < notifications@github.com> wrote:
I have experienced something like this myself when installing multiple NuGet packages in succession.
When I installed them one at a time, trying to build the solution with compile errors and everything in between, it seemed to work as it should.
My guess is that VS2017 does not flush its in-mem project model to the .csproj file often enough, resulting in somehow "overwriting" what would become the
element in the .csproj file had it been saved. Did you by any change first Install-Package Rebus -pre and then immediately after Install-Package Rebus.SqlServer -pre?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/rebus-org/Rebus.SqlServer/issues/8#issuecomment-293684950, or mute the thread https://github.com/notifications/unsubscribe-auth/AAHkeqTEEAA_XSt8f_WCmkGl3wpWPvsXks5rvSgOgaJpZM4M61Vp .
but pretty sure I did install in the order you mentioned
but did you save the project (either by explicitly saving it, or by building the project) between installing the two packages?
I think there is a bug that "forgets" to add the <PackageReference>
element when the project file is not saved to disk between installing NuGet packages.....
Closing it because it didn't really seem to be an issue 😄
(if you disagree, please reopen or attach some more comments in here...)
Spot on, sorry, should have closed it out myself.
On Sun, 30 Apr 2017 at 7:45 pm, Mogens Heller Grabe < notifications@github.com> wrote:
Closing it because it didn't really seem to be an issue 😄
(if you disagree, please reopen or attach some more comments in here...)
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/rebus-org/Rebus.SqlServer/issues/8#issuecomment-298222397, or mute the thread https://github.com/notifications/unsubscribe-auth/AAHkeoIF-OqG1Sn7U9mUsF66gN9AWw3eks5r1FhWgaJpZM4M61Vp .
This was an oddity, not really something that needs to be fixed, but I just thought I would note it here in case someone else comes across it.
For some reason, in VS 2017 after I loaded the .net core version of Rebus and Rebus.SqlServer, Visual Studio did not see Rebus.SqlServer, and I couldn't hook up the transport.
After restarting VS, it all seemed to work as it should.