Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate whether a ProjectSchemaDefinition can be used to provide automatic codegen for .bond file in the new .NET Core project system #636

Closed
chwarr opened this issue Oct 6, 2017 · 0 comments

Comments

@chwarr
Copy link
Member

chwarr commented Oct 6, 2017

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 the Compile 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).

chwarr added a commit to chwarr/bond that referenced this issue Feb 27, 2018
* 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.

Fixes microsoft#636
@lalo lalo closed this as completed in a8821da Mar 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant