search

hilkoc / vbaDeveloper

Tools for development and version control of vba code
MIT License
516 stars 137 forks source link

Excel insists on saving vbaDeveloper.xlam to AddIns directory #7

Open rmzelle opened 9 years ago

rmzelle commented 9 years ago

I tried building the addin, but when I get to step 7 ("In VB Editor, menu File-->Save Book1; Save as vbaDeveloper.xlam in the same directory as 'src'"), Excel insists on saving the .xlam file to its own AddIns directory (C:\Users\($username)\AppData\Roaming\Microsoft\AddIns), even though I select the parent directory of "src" as the save location.

If I then try to run testImport() for the installed addin, I get the error:

Folder does not exist: C:\Users\($username)\AppData\Roaming\Microsoft\AddIns\src\vbaDeveloper.xlam\
No import directory for project vbaDeveloper, skipping

Has anybody else run into this problem? Excel 2010, Windows 7.

NealHumphrey commented 9 years ago

I had the same problem on the same Excel/windows combo, but not on my Windows 8/2013 combo. I don't know the cause, but I was able to run the test import to build the file by making a copy in the vbaDeveloper folder, opening it directly from the Excel open dialog, importing and saving manually.

On Feb 11, 2015 4:14 PM, "Rintze M. Zelle" notifications@github.com wrote:

I tried building the addin, but when I get to step 7 ("In VB Editor, menu File-->Save Book1; Save as vbaDeveloper.xlam in the same directory as 'src'"), Excel insists on saving the .xlam file to its own AddIns directory (C:\Users($username)\AppData\Roaming\Microsoft\AddIns), even though I select the parent directory of "src" as the save location.

If I then try to run testImport() for the installed addin, I get the error:

Folder does not exist: C:\Users($username)\AppData\Roaming\Microsoft\AddIns\src\vbaDeveloper.xlam\ No import directory for project vbaDeveloper, skipping

Has anybody else run into this problem? Excel 2010, Windows 7.

Reply to this email directly or view it on GitHub.

rmzelle commented 9 years ago

I think I tried that as well. At some point, the vbaDeveloper menu showed up, and I tried exporting some VBA code. While I didn't get an error, I then couldn't find the exported code on my hard drive. And when I restarted Excel, it had loaded the version in my roaming profile again.

Cupitron commented 9 years ago

Same problem with my system: Windows 7, Excel 2007.

If I didn't save in the C:\Users($username)\AppData\Roaming\Microsoft\AddIns directory, Excel didn't recognize vbaDeveloper as an AddIn.

I tried saving in this directory, then copying the src folder to this directory and moving the vbaDeveloper.xlam file into the src folder. This made the testImport() Sub work but I never got the 'Menu' add in and I was not able to commit subversion changes.

NealHumphrey commented 9 years ago

For those that didn't get the menu, I have sporadically had it not load the menu on startup, but haven't had a chance to investigate. If you open the menu module you can manually run the Create menu macro to get it in there. On Feb 11, 2015 10:15 PM, "Dan" notifications@github.com wrote:

Same problem with my system: Windows 7, Excel 2007.

If I didn't save in the C:\Users($username)\AppData\Roaming\Microsoft\AddIns directory, Excel didn't recognize vbaDeveloper as an AddIn.

I tried saving in this directory, then copying the src folder to this directory and moving the vbaDeveloper.xlam file into the src folder. This made the testImport() Sub work but I never got the 'Menu' add in and I was not able to commit subversion changes.

Reply to this email directly or view it on GitHub https://github.com/hilkoc/vbaDeveloper/issues/7#issuecomment-74010858.