Thanks for the info.... That's what I get for expressing what I think are facts from my flawed human memory. (Perhaps it was a fact with Express 2005 editions when I first read the licenses long ago...)<br><br><div>Sorry for the blip,</div>
<div>David</div><div><br></div><div><br><div class="gmail_quote">On Thu, Aug 20, 2009 at 5:40 PM, j s <span dir="ltr"><<a href="mailto:j.s4403@gmail.com">j.s4403@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div>I don't believe that to be the case with Visual Express 2008. I don't know how previous editions work.</div>
<div><b></b> </div>
<div><b>Can I use Express Editions for commercial use?</b> </div>
<ol>
<li>
<p>Yes, there are no licensing restrictions for applications built using Visual Studio Express Editions. </p></li></ol>
<div><a href="http://www.microsoft.com/express/support/faq/" target="_blank">http://www.microsoft.com/express/support/faq/</a></div>
<div> </div>
<div>Juan<br><br><br><br></div><div><div></div><div class="h5">
<div class="gmail_quote">On Thu, Aug 20, 2009 at 4:33 PM, David Cole <span dir="ltr"><<a href="mailto:david.cole@kitware.com" target="_blank">david.cole@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="padding-left:1ex;margin:0px 0px 0px 0.8ex;border-left:#ccc 1px solid">
<div>Hold on there...</div>
<div><br></div>The Express editions are not meant to build redistributable binaries. They're meant for personal use: i.e. -- each user compiles his own code. I'm pretty sure it's a violation of the Express edition license agreement to build binaries for other people. You need at least the "Standard" edition of VS to get that capability.<br>
<br>
<div><br>
<div>HTH,</div>
<div>David</div>
<div>
<div></div>
<div>
<div><br>
<div><br>
<div class="gmail_quote">On Thu, Aug 20, 2009 at 5:11 PM, Mike Jackson <span dir="ltr"><<a href="mailto:mike.jackson@bluequartz.net" target="_blank">mike.jackson@bluequartz.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="padding-left:1ex;margin:0px 0px 0px 0.8ex;border-left:#ccc 1px solid">
<div>
<div></div>
<div>On Thu, Aug 20, 2009 at 4:06 PM, James Bigler<<a href="mailto:jamesbigler@gmail.com" target="_blank">jamesbigler@gmail.com</a>> wrote:<br>> On Thu, Aug 20, 2009 at 1:51 PM, Mike Jackson <<a href="mailto:mike.jackson@bluequartz.net" target="_blank">mike.jackson@bluequartz.net</a>><br>
> wrote:<br>>><br>>> On Thu, Aug 6, 2009 at 3:12 PM, Marcus D. Hanwell<<a href="mailto:marcus@cryos.org" target="_blank">marcus@cryos.org</a>> wrote:<br>>> > James Bigler wrote:<br>>> >> On Thu, Aug 6, 2009 at 12:10 PM, Bill Hoffman<br>
>> >> <<a href="mailto:bill.hoffman@kitware.com" target="_blank">bill.hoffman@kitware.com</a> <mailto:<a href="mailto:bill.hoffman@kitware.com" target="_blank">bill.hoffman@kitware.com</a>>> wrote:<br>
>> >><br>>> >> James Bigler wrote:<br>>> >><br>>> >><br>>> >> Well, I was using VS 2005 64 bit with SP 1. I wonder if there<br>>> >> is a similar bug or if there is something else going wrong<br>
>> >> such as what Marcus Hanwall described.<br>>> >><br>>> >><br>>> >> I am not sure what your issue is, but I know I have done this many<br>>> >> times...<br>
>> >><br>>> >> -Bill<br>>> >><br>>> >><br>>> >> I checked the version numbers of the DLLs, and even checked the md5sum<br>>> >> and everything was the same between the dlls in the WinSxS folder and<br>
>> >> the ones I'm distributing. It failed on two clean systems without the<br>>> >> vcredist install. I guess I'll run vcredist as Microsoft suggests and<br>>> >> see if I can trouble shoot later.<br>
>> >><br>>> >> It is a rather perplexing problem.<br>>> >><br>>> > The link Bill supplied has all of the relevant information. In the<br>>> > "Community Discussion" section the second comment provides three<br>
>> > possible workarounds. We are using the third of those when distributing<br>>> > Avogadro packages for Windows. The version mismatch in the manifests of<br>>> > the compiled executables and the manifest with the redistributable DLLs<br>
>> > is what causes the issue.<br>>> ><br>>> > It seems that MS has no intention of fixing this issue. We have a clean<br>>> > VM where we test new installers, as occasionally this change was lost<br>
>> > and the DLLs failed to load.<br>>> ><br>>> > Marcus<br>>><br>>> Ok, so I too have run into this problem. What is anyone doing to get<br>>> around this issue?<br>>><br>
>> I would really like a solution that did NOT involve editing anything<br>>> from VC++ install as I would have to pass those instructions on to the<br>>> next Developer. Clinton's posting about including the VCRedist.exe in<br>
>> the NSIS installer is OK by me. Is that what everyone else is doing?<br>>><br>>> Thanks<br>>> --<br>>> Mike Jackson<br>><br>> I ended up linking against the static CRT library (/MT), but that's not for<br>
> everyone.<br>> <a href="http://msdn.microsoft.com/en-us/library/ms235460.aspx" target="_blank">http://msdn.microsoft.com/en-us/library/ms235460.aspx</a><br>><br>> My next choice was going to be including the VCRedist.exe in the installer.<br>
> For some of the other projects at my company, this is what they do.<br>><br>> Here are some links I've been consulting on the subject of CRT library<br>> (conflicts with multiple CRTs).<br>> <a href="http://stackoverflow.com/questions/1075050/howto-multiple-versions-of-msvcrt9-as-private-sxs-assemblies" target="_blank">http://stackoverflow.com/questions/1075050/howto-multiple-versions-of-msvcrt9-as-private-sxs-assemblies</a><br>
> <a href="http://tedwvc.wordpress.com/2009/08/10/avoiding-problems-with-vc2005-sp1-security-update-kb971090/" target="_blank">http://tedwvc.wordpress.com/2009/08/10/avoiding-problems-with-vc2005-sp1-security-update-kb971090/</a><br>
> <a href="http://stackoverflow.com/questions/1265792/visual-studio-2005-security-updates-and-crt-dll-versions-in-manifest" target="_blank">http://stackoverflow.com/questions/1265792/visual-studio-2005-security-updates-and-crt-dll-versions-in-manifest</a><br>
><br>> James<br>><br><br></div></div>thanks for the links. Now my head is really spinning. I have VC2008<br>Express installed on WinXP SP3 and evidently the vcredist.exe is NOT<br>included with that version? At least I can not find it. So I guess I<br>
have to download it from MSDN (duh) and then manually set all the<br>paths and all that in oder to have cmake/NSIS find and include it in<br>the installer. And I thought deploying on OS X was a bit obtuse...<br><font color="#888888"><br>
Mike<br></font>
<div>
<div></div>
<div>_______________________________________________<br>Powered by <a href="http://www.kitware.com/" target="_blank">www.kitware.com</a><br><br>Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br><br>Follow this link to subscribe/unsubscribe:<br><a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
</div></div></blockquote></div><br></div></div></div></div></div><br>_______________________________________________<br>Powered by <a href="http://www.kitware.com/" target="_blank">www.kitware.com</a><br><br>Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br><br>Follow this link to subscribe/unsubscribe:<br><a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
</blockquote></div><br>
</div></div></blockquote></div><br></div>