What new feature(s) would you like to see in the add-in? Post your suggestions here.
1/19/2011 10:16:53 PM
jeremymcc
Posts: 4
|
The custom name tool capability is awesome because it allows the user to write whatever code they want to programmatically rename things. However, it is limited because you do not have enough information in all cases. For example, I may want to know the name of the actual table/entity (not just the name of the field), so that I can do things like:
if (name.BeginsWith(tableName)) {
name = StripTableName(name);
}
I know the built-in tool can already do something like that, but if you wanted to do something a little different, you would be out of luck.
I would propose adding actual object to the parameter list called NameContext, which would provide data on the table involved, whether the field is a primary key / foreign key, etc., etc. This would make it useful for almost any scenario.
|
|
0
• permalink
|
1/21/2011 7:32:27 AM
Kristofer Andersson
Moderator
Posts: 312
|
Good point. Parent object name (e.g. table name for columns) will be added to the extensibility interface in version 2.21 (next release). Other attributes such as pk/fk membership, type etc will have to wait for a later release.
|
|
0
• permalink
|
1/21/2011 4:10:55 PM
jeremymcc
Posts: 4
|
Awesome. Parent object name is the most important thing. In fact, that will solve all of the scenarios I can currently think of. Thanks for the quick response!
|
|
0
• permalink
|
1/21/2011 4:12:47 PM
jeremymcc
Posts: 4
|
It will also let me easily work around the navigation property issue (separate post), so after that change, I'll be all good. :-)
|
|
0
• permalink
|