Re: [Boost-users] Support for VS 2005 C++/CLI
I'm out of ideas. :-) There isn't anything actively CLI-hostile in the thread library as far as I know. You could try stepping into the program with the debugger and see what causes the error, but if it's the .NET loader not liking it for some reason, this might not help. You best bet is probably to report the problem to Microsoft somehow, since it seems like a legitimate regression.
Unfortunately the debugger doesn't help - the error isn't caught by the debugger as far as I can tell. I know I've seen problems with my code when using static objects in non-managed code. I think it might be related to the order in which initialization code is run. Anyone know of a good way to contact MS about compiler issues? I've tried in the past and it's never really been obvious that anyones even read my bug reports. I guess I'll start my posting in the MS newsgroups. Thanks- John
John Dunn wrote:
I'm out of ideas. :-) There isn't anything actively CLI-hostile in the thread library as far as I know. You could try stepping into the program with the debugger and see what causes the error, but if it's the .NET loader not liking it for some reason, this might not help. You best bet is probably to report the problem to Microsoft somehow, since it seems like a legitimate regression.
Unfortunately the debugger doesn't help - the error isn't caught by the debugger as far as I can tell. I know I've seen problems with my code when using static objects in non-managed code. I think it might be related to the order in which initialization code is run.
Anyone know of a good way to contact MS about compiler issues?
If you have paid for a version of Visual Studio 2005 you can call 1-800-936-5700. If you are just using the free Express edition you are mostly out of luck as far as telephone support. In either case, first post the bug on http://forums.microsoft.com/msdn/default.aspx, followed by a bug report at https://connect.microsoft.com/VisualStudio/Feedback and saying it is a blocking issue, then when the latter has been ignored long enough trying the phone number. Of course you can fo straight for the phone number also. If you mention Boost they may choose to help you by phone even if you have not paid. But normally even phone support is a long slow process where they spend lots of time duplicating the bug before they really try to find a solution to it if it is their bug.
John Dunn wrote:
Anyone know of a good way to contact MS about compiler issues? I've tried in the past and it's never really been obvious that anyones even read my bug reports. I guess I'll start my posting in the MS newsgroups.
Well... the download page for the beta SP https://connect.microsoft.com/visualstudio has a Feedback link http://connect.microsoft.com/feedback/default.aspx?SiteID=210 Since the SP is a beta, they probably pay attention to feedback from beta testers. :-)
John Dunn escreveu:
I'm out of ideas. :-) There isn't anything actively CLI-hostile in the thread library as far as I know. You could try stepping into the program with the debugger and see what causes the error, but if it's the .NET loader not liking it for some reason, this might not help. You best bet is probably to report the problem to Microsoft somehow, since it seems like a legitimate regression.
Unfortunately the debugger doesn't help - the error isn't caught by the debugger as far as I can tell. I know I've seen problems with my code when using static objects in non-managed code. I think it might be related to the order in which initialization code is run.
Typically, C++/CLI DLLs are compiled with /NOENTRY. Because of that, global static initialization does not happen. This article explains why, what, and how: http://support.microsoft.com/?id=814472 I've suffered much with this in the past. In my experiente if you try to fool the CLR and actually compile your DLL withouth /NOENTRY random things may happen from time to time. -- Pedro Lamarão
participants (4)
-
Edward Diener -
John Dunn -
Pedro Lamarão -
Peter Dimov