Ignore Add-In for now and just do it standalone. Add-in can use this code later. There are millions of .NET developers (and a few that do SAS and C#) so plenty of resources to help.   - Download VS Code of VS Community Edition (both free) - Download .NET Core 3.1+ SDK - Add the SAS dlls (reference COM tab in add assemblies, pick the following: SASWorkspaceManager, SASObjectManager, SAS). - Add nuget reference for EPPlus (handles Excel. See examples everywhere on the web) - Add other refs as needed (red squiggly lines can be hovered over and MS tool will prompt to add automatically) - Start writing code. Plenty of examples on how to interface with SAS but here is some to get you started: using SAS; .... Workspace ws = GetSasWorkspace(); var lang = ws.LanguageService; lang.LineSeparator = "\r\n"; lang.ResetLogLineNumbers(); lang.Submit(sasCode); /********************************************************************* * IMPORTANT: The following 2 lines MUST be included even though they * appear to be unused *********************************************************************/ #pragma warning disable CS0219 // Variable is assigned but its value is never used const LanguageServiceCarriageControl cc = new LanguageServiceCarriageControl(); const LanguageServiceLineType lt = new LanguageServiceLineType(); #pragma warning restore CS0219 // Variable is assigned but its value is never used lang.FlushLogLines(100, out Array carriage, out Array lineTypes, out Array lines); var lineList = lines.OfType<string>().ToList(); var typeList = lineTypes.OfType<SAS.LanguageServiceLineType>().ToList(); lang.Reset(); ... View more

Check on arbitrary number and name, copy, and looping through unknonw number of sheets. All easily done. Without knowing what is being searched for, hard to say how much effort would be involved on each one.:   As a trivial example of the ease:   var files = Directory.GetFiles(); foreach(var file in files)...do.. { file.CopyTo(....);) .NET is portable and works on all major O/Ss. The code can also run outside of SAS EG and execute SAS: bonus.    That said, proc copy is easier for SAS programs but proc import lags far, far behind behind Excel libraries such as Excel interop, EPPlus, GemBox, Aspose, etc. If the goal is simple importation of data, import works fine. If complex logic is needed based upon worksheet contents, you need to be able to work at the cell level (colors, fonts, placement, etc.).   ... View more

BTW, what can .NET do with SAS? EG is written in C#. ... View more

Yes, you can do this but it is not as straight-forward as you may want. First of all, not everything in EG is built-in. They specifically allowed EG to be extended with custom tasks. i have built several and Chris H has a number of examples on his EG custom tasks posts. You have to keep in mind that EG custom tasks are written in C#, not SAS (do not use the VB.NET examples). That said, C# provides all of the interfaces to SAS. So, now the general solution using a .NET custom task:   1. Create an EG custom task (see Chris Hemendinger's articles on it) 2. Use EPPlus for Excel work (free for most use). 3. Use .NET to transfer the files to your machine/server as needed. This is trivial 4. Use EPPlus code to examine the files and make decisions on where they land, folder-wise 5. Use EG interfaces to server to instruct it to execute the programs     Remember, if EG can do something, you can pretty much do it in a custom task (rule of thumb, not absolute)   Using .NET to submit code, generate SAS code, examine logs, route SAS output is absolutely possible. I do it all of the time. Does it have a learning curve? Sure but then the world of SAS is yours and you aren't restricted in power. ... View more