PowerToys for the Visual Studio 2005 Class Designer and Distributed System Designers

PowerToys for the Visual Studio 2005 Class Designer and Distributed System Designers

• Jagadeesh Aithal

  Love the plugin.  Great job!  The main reason I used it was to filter out private/internal members so I could see our public API.  Saved me lots of hassle.  Thanks
  
  

• Ezero

  I think I may have found a bug.
  
  I have a super and sub - Interface (just as is,, so maybe my code is wrong. Note: I do not use this coding style in real life, i just tried to make it as compact as possible):
  

  interface ICommand{
  void Execute(); }

  
  

  public interface ICommandSession : ICommand {
  IRCSession Session { get;set;}}
  
  I have this class:
  

  class ActionCommand :ICommandSession{
  private WinIRCLib.IRCSession session = WinIRCLib.IRCSession.Session();
  private string message = "";
  private string dest = "";
  
  

  public string Message{get { return message; }set { message = value; }}
  public string Dest{get { return dest; }set { dest = value; }}

  public ActionCommand(string dest, string message){
  this.dest = dest; this.message = message; }

  #region ICommand Members
  public void Execute() {
  session.Action(this.dest, this.message);}

  #endregion
  

  
  #region ICommandSession Members
  public WinIRCLib.IRCSession Session{
  get { return session; }set { session = value; }}
  #endregion
  }
  

  
  On the designer:
  1 - Drag ICommand onto surface
  2 - Drag ICommandSession onto surface
  (Inheritance line happens)
  3 - Drag ActionCommand
  4 - Right -click ActionCommand
  5 - Choose Show | Inheritance
  
  A duplicate object appears represending ICommandSession, so there are two on the designer now.
  

  
  

• Mark Sterin [MSFT]

  This is awesome. thanks.
  

• cbnicholson

  Doh, should have figured that out myself. It worked, thanks!
  
  Cheers
  Daniel
  
  
  
  

• ssroy

  Hi Marcel,
  
  The J# requirement was added by the MSI project I used to create the installation. I'll investigate whether I can get rid of it (it's not actually used by the add-in directly) for the further updates of the add-in. For now you'd need to install it though.
  
  Regards
  

• Shane McRoberts MSFT

  Hi Daniel,
  
  I'm glad you like the tools - I tried to include some of the features you've described on your blog ;-)
  
  The DLL you mentioned can be found in the %ProgramFiles%\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies folder - unfortunetely you'll have to fix the project by hands (or you can just add a reference path to that folder to your project so that it resolves automatically).
  
  Alternatively you can remove file ModelingTools\ClassDesignerEnhancements\CreateTestsCommand.cs from the add-in source code as this is the only file which requires it. With that you will loose Create Tests... command though. The nice thing about the add-in source code is that every feature is pretty isolated - you can add/remove features without affecting the other features for the most part.
  
  HTH
  
  Thanks
  
  

• Yottie

  Does this plugin work with VS 2k5 RC 1

  
  

• Jay Shanker

  A new build of the PowerToys which works with Visual Studio 2005 final product release is now available from http://www.gotdotnet.com/workspaces/workspace.aspx id=fe72608b-2b28-4cc1-9866-ea6f805f45f3.
  
  Enjoy!
  
  

• Thoraddict

  The MSI works fine (good job!) but I am having trouble with the source.
  
  ClassDesignerEnhancements.CreateTestsCommand references a namespace Microsoft.VisualStudio.QualityTools.Vsip
  
  Any idea which assembly I must reference to get the above to compile I cannot find Microsoft.VisualStudio.QualityTools.Vsip
  
  I have Beta 2 Team Suite on English XP Pro...
  
  FYI, the only other (solvable) glitch was having to refresh the references for EnvDTE and EnvDTE80
  
  Cheers
  Daniel
  
  

• dEcib3L

  I can't install the MSI because I did not install J#.
  
  Can somebody tell me why I would need J# to have this installed
  
  thanks
  
  

• Sahil

  Unfortunately this is not supported, for two reasons:
  1) Adding a property that is reverse-engineered from code: This will require changes in back-end model to actually support reverse-engineering the property, which is not possible with current extensibility model.
  2) Adding a property that is not reverse-engineed from code: This will require changes in serialization format of .cd file so that the property can be saved and preserved on diagram reopen. Changing serialization format is not support with current extensibility model either.
  These are all due to time constraint for this release. We will definitely consider a better extensibility model in the next release. Thanks!
  
  

• Vedran951

  Hi,
  Is it possible to add new properties to elements of the Class Designer (Enum, Inteface, Class, etc.) that appear in the Properties Window with a Custom Add-in
  If so, how could i proceed
  Thanks!
  Mike
  

• Gary Ng

  ok,
  Great,
  thanks
  
  

• ZeeshanHashmi

  Excuse me for being dense, but where exactly is the documentation for your great PowerToy installed   I've been poking around the contents and searching, but haven't had any luck.
  
  Thanks!
  
  Jim
  
  
• PowerToys for the Visual Studio 2005 Class Designer and Distributed System Designers