Thanks, it looks like promising solution!
However I found one not fully solved issue with it.. It copies all needed files correctly and it works in general, but it still adds a package reference to not existing package inside generated *.nuspec file.
Trying to restore "master" NuGet package from Visual Studio - it's trying to find the dependent (not existing) package, and obviously fails. However if I add the "master" package manually through *.csproj file - it's added and can be successfully restored. There is also no resolved code - so everything works. Except some better tooling support..
Nevermind.. seems like "ProjectB.dll" did the work, and now it works more correctly. I just didn't want to reference a dll in a "hardcoded" way initially..
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks, it looks like promising solution!
However I found one not fully solved issue with it.. It copies all needed files correctly and it works in general, but it still adds a package reference to not existing package inside generated *.nuspec file.
Trying to restore "master" NuGet package from Visual Studio - it's trying to find the dependent (not existing) package, and obviously fails. However if I add the "master" package manually through *.csproj file - it's added and can be successfully restored. There is also no resolved code - so everything works. Except some better tooling support..
Nevermind.. seems like "ProjectB.dll" did the work, and now it works more correctly. I just didn't want to reference a dll in a "hardcoded" way initially..