What is the scope of Excel add-in's and VBA references? -


How long do the rules / mechanisms add up when I install an add-in (through the checkboxes) -Have it installed? It appears that it is installed at the application level, which means that it applies to any workbook in Excel application, unless you uncheck it yourself. If this is true, then this means that until a user installs the add-in, they should be correct; But they will have to install it for the first time (which can be done programmatically).

Regarding VBA contexts, I think that they do not need to 'check' every time - which means it is within the scope of the document. But if this is true, why do the websites advise to use late binding methods to be distributed? In fact, it is actually late for being compatible with different versions, but it is not necessary that DLL has been referred as a 'check'? Under this assumption, unless someone uses the same version of Excel, it would be safe to leave all the binding together, and just manually add the reference?

The add-in is installed at the application-level

As long as a user adds to himself, you can fix how an add-in can be shown in front of various workbook (o) (or not). They should be fine; But they must first install it

Yes, they have to install it.

Regarding VBA contexts, I think that not every time it needs to be 'checked' - which means that it is within the scope of the document.

Yes, version control also saves you the hassle of trying and adds context to the programs. It can be done by this path (which is necessary to know the OS, version, etc.) or the GUID (I have not really been able to do this successfully) both of these need to make a mistake (what if the path Does not exist or is otherwise unusable? Etc). So just use late binding.

It is useful to help in using initial binding from a user's perspective, although the EB is reasonably fast, but generally there is no difference between it. Usually negligible for most applications. Related, if you rely on the new keyword to instantiate objects while using EB, then I believe that the one you use with the Lb is CreateObject function is really fast. This is probably not worth the attention, though.

Can I finally leave everyone together by being bound, and be safe by adding context manually?

Just develop with EB, and then modify the code in late bound objects before compiling the add-in.

Comments

Popular posts from this blog

java - ImportError: No module named py4j.java_gateway -

python - Receiving "KeyError" after decoding json result from url -

.net - Creating a new Queue Manager and Queue in Websphere MQ (using C#) -