copy dll from server to local to run ...opinions

[mpropst]

I found that dotnet apps don't want to run from server without some tweaking of gac or some other things i don't understand, and don't want to mess with server settings..

what is the typical way of deploying a dot net app in a small office? 3-4 users

i was considering this lisp to copy latest server version to local drive,

opinions?

(defun LoadAppFromServer()
 (setq ServerCopy "Path to server copy\\app.dll")
 (setq LocalCopy "C:\\Local path\\app.dll")

;Delete local copy to ensure latest version
 (vl-file-delete LocalCopy)

;Try to copy server copy to local drive
 (if(vl-file-copy ServerCopy
           LocalCopy)
  (progn
   (setq FileName LocalCopy)
   (princ (strcat "\ncopied source file " ServerCopy " from server"))

   (if (findfile Filename)
     (command "netload" Filename)
    (princ(strcat("\nFile not found" Filename)))
   )
  )
  (progn
   (princ (strcat "Failed to copy source file " ServerCopy " from server"))
     )
 )
 
)
;(LoadAppFromServer

[caddzone]

The easiest way is to add some scripting to the user's login script that

compares file timestamps and copies newer files from the server to

the local system.

[mpropst]

i don't currently have login scripts, though i could research that.

would it be functionally equivalent if i  just putting that lisp in acad.lsp so it just runs once per session?

pros / cons ?

did that lisp code look ok? it works here so far but are there obvious flaws?

(other than it's not checking dates so i have to add that) but as far as deleting the old and copying the new?

thanks

[andrewpuller3811]

You might want to check the server file exists before you delete the local file.

[mpropst]

Andrew, good point, I know it does, but should add that to the code, thanks

mark