Topic: how to load a dll into AutoCAD from http or ftp

[michiel]

Thx guys it works.

now I just have the problem that the dll is stored on the local computer in some directory of windows, but I can't find it, because when I load the dll from internet, it works fine the first time, I shut down my internet connection, and then I startup my program again, from the internet source and it still works...

Where is it stored? c:\windows\assembly ? C:\Windows\Microsoft.NET\assembly?

Is it possible to just load the dll in the instances of AutoCAD and is protected?

Someone has an answer on this?

[vegbruiser]

You only want to allow the application to run when there's an active Internet connection? That would mean (I guess) that you'd have to prevent the remote .dll file from being cached locally (to the user)?

And sounds more and more like you'd be better off tying your users to a "service" rather than a specific file?

[michiel]

You only want to allow the application to run when there's an active Internet connection? That would mean (I guess) that you'd have to prevent the remote .dll file from being cached locally (to the user)?

Yes... any idea how I can implement this?

And sounds more and more like you'd be better off tying your users to a "service" rather than a specific file?

And how would you suggest me to do that?

thanks in advance!

[Kerry]

Frankly I'd be very reticent about using ANY DLL that required a connection to the internet so it could be downloaded every time I choose to use it. 

Firstly, it's inconvenient.
Secondly , and most important it's dangerous (FOR ME) to load a dll that is likely to change at each invocation.

Just my opinion.

Regards
 

edit:fixed laptop spelling

[Draftek]

Looks like you have 2 good options:
1. Create and consume a web service.
2. Download the file yourself and load it with a byte[] arrary

[dgorsman]

Option 3: download the DLL once, and periodically use the internet to validate licensing and maybe download some critical data.  Data transfer is easier, not to mention safer.  Still presents problems e.g. down/upload caps, plus many will never trust something so dependant on phoning home.

[Draftek]

^ Good idea.

I personally use option 1 and 3.