Deployment path settings
When deploying the database project, you should have the option to select where to deploy at that time. Currently, the selection is made at the project scope.
It is very common in my usage even so far to deploy a database to more than one location. I may create a database model and deploy it to four servers: production, test, development, and to the developer's local pc.
Even if you leave the default deployment path setting in the project properties, there should be a confirmation form appear when you choose Deploy Selection and that form should show the default deployment path but have the option to modify the setting for the current deployment and, optionally, to save the modification as a new project scoped default.
Can I make a couple other suggestions about the build process from a user perspective without losing you here?
There is no "rebuild option" and the build toolbar buttons (both for project and solution) do not appear to work in the CTP.
Along the same lines, the phrase Deploy Selection is confusing. Because of the phrasing, I opened a stored procedure file that had been modified, selected the text, and then right clicked the project and chose "Deploy Selection" thinking it would deploy my stored procedure change. It didn't. It deployed the whole database which was fine but confusing.
Would Deploy Solution or Deploy Project be clearer?
[1445 byte] By [
Dale] at [2008-2-5]
Dale -
I'm one of the writers working on the content for Team Edition for Database Professionals. I've had similar concerns about the "Deploy Selection", so we'll see about modifying that. If we're consistent with the other build options, it should read 'Deploy ProjectName', where ProjectName is the database project name.
When I use the build toolbar, I'm seeing both buttons building my selection, rather than building the selected project and the entire solution, respectively. I'll get a bug filed on that :).
I am seeing a rebuild option on both the Build menu and the Project and Solution context menus. It does not appear on the toolbar (to be honest, I don't think I'd ever used the build toolbar, tending to use the menus instead).
If you have suggestions about the docs, feel free to pass those along as well.
-Steven Powell
Thank you for your reply, Steven.
Most people probably don't use the build toolbar because it is not shown by default. I just automatically add that and the "Close All" Windows toolbar button to my environment.
I have seen a rebuild option in the menu from time to time but haven't figured out what makes it come and go. I believe that previously published usability guidelines have suggested that menu options be disabled rather than removed when they're not appropriate to the current state.
Let me just say that the project seems to hold great promise. I am very excited about it. It was a key driver in my decision to upgrade my MSDN from the developer edition to team suite. -- now I just hope that it gets released before my subscription expires.
Thanks,
Dale
