The question think we need answered is what exactly do you want:
1. An archive button to archive the current drawing.
a. Automatically archive when saved
b. Only when prompted to do so.
c. Manual archive only
2. Archive an entire project at a time.
a. Archive entire project
b. Archive only drawing files.
Are you going to allow the user to do this or will someone else.
Do you need the program to run in AutoCAD? How are going to handle files in use?
If your going to Queue the files you can store all this info into the systems registry / text file / database
and then build and export the files in the queue and a predetermined time.
You need to be very clear about the steps you expect the program to do.
If I've got my head wrapped around this correctly, you are not going to be able to have AutoCAD save the Drawing to the final Archive location, because AutoCAD will not be running under the proper identity to perform the save, so AutoCAD will have to save the drawing in the working location, then your separate program will be fired off under the different identity, and copy (or move) the file to the Archive location.
All this is doable. You might not even need a .NET program to run in AutoCAD. You can put a save and a shell execute into the button code, but I'm not sure how you are planning on getting the .EXE running under different credentials. I believe there is a way to do it in .NET code, but I had one chance to look into a couple of years ago, and about one day to play around with it, and while my code executed, it did not execute under the admin credentials like I was trying to make it, so we used a different solution.
This migh tgive me an excuse to look into it again.
Yes, that's the idea. I plan on having the user click a menu choice which will startapp a separate .NET exe. And you're also right the AutoCAD will not be running with the proper credentials to handle the file save. Thus the need for a stand-alone EXE.
For example, I have a custom menu in all the users' setup now and one of the choices is to enter a new drawing into an Access database. The users enjoy this very much because it controls the environment and they can't hack up the database. It launches a stand-alone exe which is a form they use and it allows the get the next drawing sequence number as well as enter data about their new drawing. And they never have to run Access at all. It works slick.
I'm attempting the same thing here. Again on the surface it looks whack-o but there really is a method to the madness. I will post back later when I get to my home office. Thanks again, I really appreciate all the tips and advice.
Check out the Autodesk developer Network page here http://usa.autodesk.com/adsk/servlet/index?siteID=
It has links to the 2013 dot net training labs and other 2013 specific documentation.