| Author |  Topic  |  | 
              
                | GavinErryNew Member
 
  
 
                4 Posts | 
                    
                      |  Posted - Jul 11 2004 :  01:37:34 AM   
 |  
                      | Hi 
 I've just been evaluating your add-in, and found a problem.  As it happens I was programming an add-in of my own, and found that this piece of code produces unusual results when Visual Assist is present.
 
 pdocument is a pointer to a Document object in EnvDTE
 pdocuments is a pointer to a Documents collection in EnvDTE
 filename is a CString containing the filename
 
 // Add a new document to the list
 pdocument = pdocuments->Add ( "Text" );
 
 // Name, save and close the new file
 status = pdocument->Save ( static_cast<_bstr_t> ( filename ) );
 pdocument->Close ( EnvDTE::vsSaveChangesYes );
 
 This code should add a new file to the Documents collection, and save it with the appropriate filename.  Without Visual Assist this works.  When Visual Assist is running a Save As dialog box appears wanting me to save a file 'TextFilen.txt' (n is a number) to the project directory.
 
 I have tried both builds 1244 and 1246, and this issue appears.
 
 Any ideas?
 
 Gavin
 
 |  | 
              
                | supportWhole Tomato Software
 
      
 
                5566 Posts | 
                    
                      |  Posted - Jul 11 2004 :  11:05:29 AM   
 |  
                      | Workaround is to disable VA X using "VAssistX|Enable" before running your add-in. |  
                      | Whole Tomato Software, Inc.
 |  
                      |  |  | 
              
                | GavinErryNew Member
 
  
 
                4 Posts | 
                    
                      |  Posted - Jul 11 2004 :  3:28:12 PM   
 |  
                      | Unfortunately, disabling Visual Assist does not fix the problem. 
 Gavin
 
 |  
                      |  |  | 
              
                | GavinErryNew Member
 
  
 
                4 Posts | 
                    
                      |  Posted - Jul 11 2004 :  5:11:37 PM   
 |  
                      | Sorry - should have said that disabling VA does not work, but uninstalling VA fixes the problem. 
 Gavin
 
 |  
                      |  |  | 
              
                | supportWhole Tomato Software
 
      
 
                5566 Posts | 
                    
                      |  Posted - Jul 12 2004 :  2:23:24 PM   
 |  
                      | If you do not need to run your add-in often, you might try unloading VA X prior to running it. Assuming VS.NET, see Tools|Add-in Manager. 
 Unload VA X. (Leave startup checked.)
 Run your add-in.
 Restart your IDE. (Keeps the IDE stable.)
 |  
                      | Whole Tomato Software, Inc.
 |  
                      |  |  | 
              
                | GavinErryNew Member
 
  
 
                4 Posts | 
                    
                      |  Posted - Jul 14 2004 :  01:03:06 AM   
 |  
                      | Nope - that doesn't fix it either... 
 Gavin
 
 |  
                      |  |  | 
              
                |  |  Topic  |  |