<div dir="ltr">Thank you for the quick reply.<div>I didn't have any issues with the build, basically everything worked as described in the readme. We haven't done much testing though so I'm not sure about the funcionality. I checked the VS and we do have update 4 so I hope that's fixed. I'm going to check up on the bug anyway just to be sure. Once we've done some testing, I will let you know.</div><div>Adam</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Nov 20, 2014 at 4:35 PM, Daniel Krügler <span dir="ltr"><<a href="mailto:daniel.kruegler@gmail.com" target="_blank">daniel.kruegler@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">2014-11-20 16:20 GMT+01:00 Adam Manca <<a href="mailto:darkenned@gmail.com">darkenned@gmail.com</a>>:<br>
> We are using Corba but it's been some time since it was updated (using<br>
> 4.1.3). Also the project itself is a bit older and we are considering<br>
> upgrading to VS2013. So, to my question: does anyone have any experience<br>
> using omniORB in VS2013 projects?<br>
<br>
</span>We have build OmniOrb using Visual Studio 2008 and 2012. The build<br>
process is not trivial IMO and I would be very happy to see a<br>
cmake-based build, but it works.<br>
<span class=""><br>
> I saw some posts about compiling it from<br>
> the source (I did that too, used Python x86 and used the vc10 config -<br>
> simply copied it and renamed to vc12). However, noone posted after that,<br>
> whether it's actually working without any issues.<br>
<br>
</span>With OmniOrb 4.2 we stumbled across one severe issue that is described<br>
in this posting:<br>
<br>
<a href="http://www.omniorb-support.com/pipermail/omniorb-list/2014-November/031627.html" target="_blank">http://www.omniorb-support.com/pipermail/omniorb-list/2014-November/031627.html</a><br>
<br>
I have been told (search for feedback id 1033845 in the Microsoft bug<br>
tracking system) that the mentioned incorrect behaviour of Visual<br>
Studio that nastily interacts with the definition of the mentioned two<br>
OmniOrb macros should be fixed in VS2013 update4. We have not the<br>
luxury to switch to VS2013, so this is no option for us (so I strongly<br>
hope that OmniOrb will fix the macro definitions), but if you have<br>
this compiler you should ensure that you have at least this update<br>
version of the compiler.<br>
<br>
HTH & Greetings from Bremen,<br>
<br>
Daniel Krügler<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"> S pozdravom,<br>Adam Manca<br></div>
</div>