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
As reported in #634, installing the Bond.CSharp NuGet package doesn't provide the BondCodegen build action. (Reloading the solution sometimes makes this available.) There's an open feature request in the .NET project system to make AvailableItemName work again.
We should investigate whether this is something that can be included in the NuGet package for the project system to pick up. If it can, it would make .bond files in the project directory automatically run codegen, which would be better than what happens today (nothing).
The text was updated successfully, but these errors were encountered:
* Enabled automatic codegen when implicit inclusion is turned on via the
MSBuild property EnableDefaultCompileItems
* Added Visual Studio CPS UI integration so that .bond files appear in
the Visual Studio 2017+ UI.
Fixesmicrosoft#636
As reported in #634, installing the Bond.CSharp NuGet package doesn't provide the BondCodegen build action. (Reloading the solution sometimes makes this available.) There's an open feature request in the .NET project system to make
AvailableItemName
work again.The new project system appears to use
ProjectSchemaDefinitions
to do things like automatically cause .cs files to be added to theCompile
item.We should investigate whether this is something that can be included in the NuGet package for the project system to pick up. If it can, it would make .bond files in the project directory automatically run codegen, which would be better than what happens today (nothing).
The text was updated successfully, but these errors were encountered: