Can I put a .NET Framework DLL into a GitHub Package, that accesses MS Outlook? #54283
Replies: 1 comment
-
I think the answer is the GH Package is included during the build, rather than being an API. If this is wrong, please correct me. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Select Topic Area
Question
Body
I'm still trying to wrap my head around GitHub Packages. One of my colleagues wrote a .NET Framework (4.5.2, I think) DLL that launches Microsoft Outlook on the user's machine, then sends an email, optionally with an attachment. But what he did was save the DLL and then copied that into several other Visual Studio projects. Thus, it is in several TFVC repos. We're migrating our TFS repos to GitHub and I'd rather not copy DLLs into the new Git repos in GitHub if I can avoid it.
Now here's the part that I don't completely understand. Is the DLL, in a GitHub Package, like an API? If it is, then I don't see how that would work. The API won't be running on the users' machines, so it can't access Outlook.
If on the other hand the DLL in a GitHub Package is something that can be included during a build (and hopefully included both for the developer as well as a GitHub Action), then I would think the resultant .EXE would have access to Outlook on the users' machines.
Which is it, please?
Beta Was this translation helpful? Give feedback.
All reactions