Timeline for Source Control and custom VBA Code Exporter
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 12, 2019 at 10:27 | comment | added | FlameHorizon |
That's correct. When I import back modules into VB Project I use VBProject.VBComponents.Import(FilePath). This this lets me avoid problems with attributes.
|
|
| Dec 11, 2019 at 19:45 | comment | added | Mathieu Guindon | One more thing - the VBIDE API will export module/member attributes for document modules, but since they can't be imported back in, they shouldn't be exported at all - FYI Rubberduck's bulk-export functionality doesn't have this problem, but exporting individual modules does | |
| Dec 10, 2019 at 6:45 | vote | accept | FlameHorizon | ||
| Dec 8, 2019 at 11:33 | answer | added | FlameHorizon | timeline score: 2 | |
| Dec 8, 2019 at 6:00 | history | tweeted | twitter.com/StackCodeReview/status/1203554907900514304 | ||
| Dec 7, 2019 at 19:59 | answer | added | Mathieu Guindon | timeline score: 3 | |
| Dec 7, 2019 at 16:08 | comment | added | Mathieu Guindon | Did you know Rubberduck provides this bulk import/export functionality out of the box? (no need to trust programmatic access to the VBIDE API library!) | |
| Dec 7, 2019 at 12:45 | history | asked | FlameHorizon | CC BY-SA 4.0 |