An MSVC environmental question

Question

0.00/5 (No votes)

See more:

I like so many other developers, develop useful tools which could be contained within these windows DLL files. But the question is; how can we(as developers) add our own new software API's up under our MS Visual Studio environment(s), so we can again come up with new software applications? It's like our new software tools are now new API's?. How's this done? I'm not a state of the art programmer like I see so many others are, I usually learn and experiment by the seat of my pants, and it usually works. I'm asking for a little patience and understanding in answering this question on hows to do it. I really could use some help. Again, thanks...

What I have tried:

As to what I've tried, I don't even know where to start.

Posted 15-Dec-21 12:17pm

Member 15028314

Updated 15-Dec-21 20:07pm

Add a Solution

Comments

Shao Voon Wong 16-Dec-21 2:38am

You can write a Visual Studio Extension to extend its functionality if that's what you meant by using your APIs.

https://docs.microsoft.com/en-us/visualstudio/extensibility/getting-started-with-the-vsix-project-template?view=vs-2022

Member 15078716 11-Jul-22 2:43am

@Shao Voon Wong, Nice. I had not seen this before. I looks useful. +5 to you if I could figure out how to give it.

Rick York 16-Dec-21 11:04am

The general term used for this is "plug-ins." Applications define an interface for DLLs and their functions to adhere to and the app can dynamically load plug-ins and use their interface.

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)