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

Angular Template Not Auto-Incrementing Version & Missing Project Properties #272

Open
4 tasks
WillStrohl opened this issue Aug 30, 2023 · 0 comments
Open
4 tasks
Labels
bug Something isn't working sponsors welcome The effort required would make a sponsor the ideal approach to closing this issue.

Comments

@WillStrohl
Copy link
Contributor

Sponsorship

If this request requires additional support (e.g., such as direct email/phone/meeting/development), I have the following interest in helping to sponsor the effort via GitHub Sponsors:

  • None, please continue to work for me for free :P
  • Absolutely, I get value out of this!
  • Maybe later
  • I'm already a sponsor... Woot!

Describe the bug

A clear and concise description of what the bug is.

Software Versions

  • DNN: N/A
  • Hotcakes: N/A
  • Visual Studio: N/A

To Reproduce

Steps to reproduce the behavior:

  1. Latest generator...
  2. Go through the steps to create an Angular project.
  3. Open it in VS.
  4. Build in debug, then release mode.
  5. Change the version in the package line of the main manifest file.
  6. Rebuild in release mode.

Expected behavior

The resulting project should have an AssemblyInfo.cs class, resulting in a Properties menu/file item in Solution Explorer.
After the second build, the version numbers should have incremented the same as other projects, in both manifests and in the AssemblyInfo.cs file.

Actual behavior

The version numbers are untouched, and the AssemblyInfo.cs file is missing.

Screenshots

N/A

Error log

No errors.

Additional context

None.

@WillStrohl WillStrohl added bug Something isn't working sponsors welcome The effort required would make a sponsor the ideal approach to closing this issue. labels Aug 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working sponsors welcome The effort required would make a sponsor the ideal approach to closing this issue.
Projects
None yet
Development

No branches or pull requests

1 participant