![]() Just curious as it is obvious that a lot of people feel this is needed and and we have been on DB Projects for 3+ years and have a very thorough understanding of that technology. No cross reference databases without the enormous overhead of partial projects treating database projects and solutions like an object oriented project. The projects enforce rules within a solution that are not relative to the real world and the performance overhead is excessive in a large environment. ![]() Actually the reason we are moving from them is the fact they are too advanced. For those that are needing RG to work with a DB Proj setup I would like to ask why? If you are currently using the VS DB projects what functionality would you expect the RG tool to provide? The DB projects are already contain very advanced features. We are working towards migrating to SSC and providing a substantial amount of feedback to RG in regards to SQL Connect. Shared Projects do have less suggestions when 'Add -> New Item.' as they are more generic. We currently use VS DB Projects on a large dev team in an enterprise environment. Files in Shared Projects can use code from projects where the Shared Project is added as a reference if all of those projects do have the code to be used. Sorry I couldn't help more with SSDT but for now we are focusing on implementing a tool that doesn't hinder our productivity. MS has a tendency to focus on the volume distribution of their products vs value and function. RG seems to understand enterprises much more than MS. The simplicity and the approach that RG takes to mimic what SQL Server actually does is what is attractive to our teams. The tool works great if it is a very small database that is created within the tool from the inception. In all honesty, the current version works and does what it does quite well, but with our experience it is a tool that is targeted for existing enterprise environments. We decided to not take our chances with the next version since the original version was released with so many issues and concerns. We have worked with many individuals from MS, including some of the project managers directly, and the voice/concerns were never heard. ![]() We have fought through the current iteration of MS DB tools since their first version. ![]() (You can right-click the project node and select Add from the fly-out menu to choose from these options, too.). We have not looked into or researched the SSDT tools. In Solution Explorer, right-click the References or Dependencies node, and then choose either Add Project Reference, Add Shared Project Reference, or Add COM Reference from the context menu. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |