| Design time control of published runtime artifacts [message #1761248] |
Tue, 09 May 2017 11:09 |
 Georgi Pavlov
Messages: 39
Registered: October 2014 |
Member |
|
|
Currently, the published application artifacts are not bound to the design time projects where they originate.
With this strategy, it becomes a seriously tedious task to design things at macro level. For example, a simple copy->paste->rename of an artifact (that you'd do to save time) results in two artifacts, one of which you totally don't need and you need to go to the repo to clean it up manually. If you do that for an extension then it becomes even more difficult to manage and so on, and so forth.
The point is that we need to seriously reconsider the control on the application artifacts from the design environment. If I delete or create new objects I'd like to have much better control on how things end up in the runtime and my expectation would be that it reflects more strictly my designtime.
|
|
|
Powered by
FUDForum. Page generated in 0.02949 seconds
] 
Search
Help
Register
Login
Home
