15,894,330 members
Sign in
Sign in
Email
Password
Forgot your password?
Sign in with
home
articles
Browse Topics
>
Latest Articles
Top Articles
Posting/Update Guidelines
Article Help Forum
Submit an article or tip
Import GitHub Project
Import your Blog
quick answers
Q&A
Ask a Question
View Unanswered Questions
View All Questions
View C# questions
View C++ questions
View Javascript questions
View Visual Basic questions
View Python questions
discussions
forums
CodeProject.AI Server
All Message Boards...
Application Lifecycle
>
Running a Business
Sales / Marketing
Collaboration / Beta Testing
Work Issues
Design and Architecture
Artificial Intelligence
ASP.NET
JavaScript
Internet of Things
C / C++ / MFC
>
ATL / WTL / STL
Managed C++/CLI
C#
Free Tools
Objective-C and Swift
Database
Hardware & Devices
>
System Admin
Hosting and Servers
Java
Linux Programming
Python
.NET (Core and Framework)
Android
iOS
Mobile
WPF
Visual Basic
Web Development
Site Bugs / Suggestions
Spam and Abuse Watch
features
features
Competitions
News
The Insider Newsletter
The Daily Build Newsletter
Newsletter archive
Surveys
CodeProject Stuff
community
lounge
Who's Who
Most Valuable Professionals
The Lounge
The CodeProject Blog
Where I Am: Member Photos
The Insider News
The Weird & The Wonderful
help
?
What is 'CodeProject'?
General FAQ
Ask a Question
Bugs and Suggestions
Article Help Forum
About Us
Search within:
Articles
Quick Answers
Messages
Comments by Peter Abbasi (Top 7 by date)
Peter Abbasi
3-Dec-23 21:36pm
View
Wow. Thanks, Andre. This was more than I was hoping for, and definitely more than I was expecting. Guidelines or not, seems like you've given me a great starting point with a thoughtfully written response. It is much appreciated.
Peter Abbasi
3-Dec-23 21:31pm
View
That just means more opportunity to learn, right? :) I get the message though. It is definitely something to consider before committing to anything, and the fair warning is appreciated.
Peter Abbasi
1-Dec-23 20:07pm
View
Thanks Maciej Los - and you are not wrong. It is a valid solution, but not everyone is able to write C#, nor is every individual in the office work setting willing to invest the time or effort into learning it. In fact, I personally know dozens of people who have full libraries of VBA macros they use to automate tasks, and they never even learned Visual Basic. Some people are just set in their ways. I could see a use case for an app like this (not that my intention is to commercialize it) but for the sake of argument, there are plenty of individuals who would rather be able to just plug in their own saved macros (of which they have a full collection) and run them that way, as well as organize, save and view them.
Your solution did bring an important point to my attention also. It was never my intention to limit my question to C#. In my first draft, my exact wording was actually "C# (or any language for that matter including C++, VB.NET, or any of the other languages that is not unusual for Windows to support)." Unfortunately, I was multi-tasking, and erased that portion of the question by mistake.
Peter Abbasi
1-Dec-23 15:12pm
View
Understood and thanks again!
Peter Abbasi
1-Dec-23 12:23pm
View
Thanks again. I'll check them both out to be safe :)
Peter Abbasi
1-Dec-23 12:21pm
View
Thank you for providing the link. I will definitely take a look! As far as needing to classify them, I am not sure if this is what you mean by classification: but essentially the app would be installed locally on the same machine as the instance of Office, the macros would be the conventional kind of document review/formatting/find and replace kind of macros you'd find in both excel and word add-in templates. Nothing crazy - the most complicated macro would likely ask for user input (a search term and replace term for find/replace). I imagine there would be two lists in the GUI, one for macros that are found in and called from excel, and the other found in and called from word. Is that the kind of classification you are talking about?
Peter Abbasi
1-Dec-23 12:14pm
View
Thanks for the suggestion, Richard.
Show More