"not valid add-in" message

[Andrew Kolesnikov]

Hello, everybody.

Recently, i've built QLXL solution, but couldn't load created add-in, cause of error message "QuantLibXL-vc90-mt-0_9_7.xll is not valid". Project was built in VC 2008 with multi-threaded dll runtime library (as recommended). I guess, that the problem occurs cause of different original VC version (i.e. 8.0), but i don't know how to fix it! Another question is about version history file, which contains recommendation to build QL within VC 2008 by using Boost 1.35 (not 1.36). For what reason?

Thanks,
Andrew.

[Eric Ehlers-2]

Hi Andrew,

Quoting Andrew Kolesnikov <[hidden email]>:
>
> Recently, i've built QLXL solution, but couldn't load created add-in, cause
> of error message "QuantLibXL-vc90-mt-0_9_7.xll is not valid". Project was
> built in VC 2008 with multi-threaded dll runtime library (as recommended).

No, the use of the DLL runtime is *not* recommended.

The instructions for building QLXL from source code are here:
     http://quantlib.org/quantlibaddin/build_qlxl.html
That tutorial advises you to use configuration "Release (static runtime)."

You say "multi-threaded dll runtime library", which is what you get  
from configuration Release.  This is not recommended as a starting  
point because your XLL then has a run-time dependency on the Microsoft  
runtime DLLs.  This can lead to the "XLL is not valid" error, for  
example if you build the XLL on one machine and try to run it on  
another - is that what happened here?

Given that you are using VC 2008, I suggest you use solution  
QuantLibXL_basic_vc9.sln, configuration Release.  The output file from  
this build is QuantLibXL-vc90-mt-s-0_9_7.xll.

Of course the DLL runtime has some advantages over the static runtime,  
and there are many applications for which only the DLL runtime is  
appropriate.  But in the simple case where you're just trying to build  
QLXL yourself for the first time, the static runtime offers fewer  
opportunities for error.

> Another question is about version
> history file, which contains recommendation to build QL within VC 2008 by
> using Boost 1.35 (not 1.36). For what reason?

VC 2008 requires boost 1.35 or later - 1.36 is OK.

Regards,
Eric

===================================================
Eric Ehlers
nazcatech sprl | Brussels | http://www.nazcatech.be
* Distributed computing for pricing analytics
* Use Microsoft Excel as a client to the Grid


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
QuantLib-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quantlib-users

[Andrew Kolesnikov]

"No, the use of the DLL runtime is *not* recommended."

I see, but possible i was tangled cause of this QL release notice:
<Microsoft Visual C++ configurations have been renamed. The default Debug and Release configurations now link to the DLL version of the common runtime library...>

" But in the simple case where you're just trying to build  
QLXL yourself for the first time, the static runtime offers fewer  
opportunities for error."

I'm not newbie in this project, and have already built different version of my own XLL library (sure, in static mode), which is based on QL, but was confused statement above. Now, all is ok.

Regards,
Andrew

[Eric Ehlers-2]

Hi Andrew,

I see - apologies for the confusion on the somewhat contradictory text
in the QL/QLXL docs.  Very glad to hear it's all working now.

Regards.
Eric

===================================================
Eric Ehlers
nazcatech sprl | Brussels | http://www.nazcatech.be
* Distributed computing for pricing analytics
* Use Microsoft Excel as a client to the Grid

On Mon, 2009-01-19 at 02:46 -0800, Andrew Kolesnikov wrote:

>
> "No, the use of the DLL runtime is *not* recommended."
>
> I see, but possible i was tangled cause of this QL release notice:
> <Microsoft Visual C++ configurations have been renamed. The default Debug
> and Release configurations now link to the DLL version of the common runtime
> library...>
>
> " But in the simple case where you're just trying to build  
> QLXL yourself for the first time, the static runtime offers fewer  
> opportunities for error."
>
> I'm not newbie in this project, and have already built different version of
> my own XLL library (sure, in static mode), which is based on QL, but was
> confused statement above. Now, all is ok.
>
> Regards,
> Andrew
>
> --
> View this message in context: http://www.nabble.com/%22not-valid-add-in%22-message-tp21502733p21540550.html
> Sent from the quantlib-users mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> QuantLib-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/quantlib-users

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
QuantLib-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quantlib-users