Trigger the function generator based on the UseNServiceBus parameters

[danielmarbach]

Describe the suggested improvement

Is your improvement related to a problem? Please describe.

This is a wild idea and we haven't investigated lot more thoughts into the feasibility of it. During discussions we wondered why it is necessary to define the endpoint name on the global attribute on the project and on the usage of UseNServiceBus. It also seems that those need to be kept in sync.

Only when you want to manually create the function definition you would want to remove the attribute which the generator is keyed off and then specify an endpoint name on UseNServiceBus that matches the configuration in the trigger you manually defined.

Technically we could key the source generator based on the parameters of UseNServiceBus which would make the attribute unnecessary and there is also no possibility to diverge anymore. Source generators have the possibility to define custom msbuild properties that would still allow disabling the source generator. The functions SDK for example provides such msbuild hooks.

Describe the suggested solution

Describe alternatives you've considered

Additional Context

No response

[mikeminutillo]

Hey @danielmarbach. Is this one still relevant? We are trying to triage the issue and we noticed that it was closed and re-opened.

[danielmarbach]

We are reworking the functions user experience quite a bit. We can follow through on this and other issues once we have that approach ready.

It was closed and reopened due to default project automations by accident.