Marcus wrote:
Frans,
I know we discussed this before when I complained about the fact that the catalog refresh on the designer was too cumbersome.
You correctly pointed out that the backup question, confirmation steps and re-connection to the database provided users with a safety net to protect the designer project from being updated by mistake.
BUT - Can you PLEASE include a feature in the next release to avoid all this? \
So just backup and connect, refresh and be done?
I want to be able to refresh the catalog using CTRL-r or something, I don't want to be asked any confirmation, I don't want any re-connection, just refresh "right now".
You could turn this feature off by default in each new project so that only experienced users would have it turned on which would provide your safely net.
No backup file also?
When I’m prototyping something or trying to get something to work, it will be refreshing tiny changes in the database multiple times and this feature would really benefit productivity…
Alt-tab from Visual Studio to LLBLGen Designer, CTRL-r to refresh and CTRL-g to re-generate no confirmations… Alt-tab back to Visual Studio… etc
generation without questions is already there set the correct generator config in the preferences, hit f7 and enter.
I'll add the cntrl-r thingy to the todo.
OR BETTER STILL VS.NET integration!!!!
Seriously: would this be a big help really? I mean: the only thing you really want is project file management: an entity gets a new code file (or set of code files) and the project has to be updated, an entity is removed and its files have to be removed from the project file as well... Everything else, the integration would only clutter the UI, as vs.net's UI is very cluttered (some properties are in the properties window, others are in popup windows, again others are in a designer in the middle pane etc..) and integration would mean: real integration: the designer will be merged with vs.net completely.
This integration is horrible to program at the moment due to vs.net's COM structure...