Hi,
Last week we upgrade Visual Studio from 2010 to 2012. Since then we noticed a small change in how the UltraMessagebox is being displayed.The margin below the buttons is gone. As a result the buttons are touching the bottom border.
After we noticed this we also upgraded Infragistics to 2012.2 but this didn't change anything.
Is there any way i can get a margin below the buttons?
Hello ,
You could avoid this with simple implementation of CreationFilter, please see attached sample.
Please let me know if you have any further questions
Solution works but still looks a bit weird and it seems to me that this is a work around instead of a permanent solution.
Would look better if it's possible to expand the button area in height. Is this possible?
My findings are that if you built a sample with Visual Studio 2012 message boxes of UltraMessageBox are smaller that this in visual studio 2010. I am not sure what is the exact reason for this issue, so I have created a support ticket in our system, its id is CAS-102871-T6N8T5. So I will investigate this further and will update you for my further finding through the mentioned support ticket.
Thank you for using Infragistics Components.
Hello,
I have just noticed this same behaviour in a project I am working on. Will this be rectified in a future release?
Thanks,
Sean
This is a Microsoft issue. The issue involves the size of the form when the FormBorderStyle of a form is changed in code, while the Visual Studio 2012 Host Process is being used.
http://connect.microsoft.com/VisualStudio/feedback/details/759413/winform-dialogs-displayed-differently-by-vshost-exe-and-exe-using-vs-2012-when-formborderstyle-set-in-form-codebehind
Please let me know if you have any further questions.
I am having the same issue even though I don't change the border style. None of the workarounds in the link work. I don't understand how this is a Microsoft issue when MessageBox.Show() works but Infragistics.Win.UltraMessageBox.UltraMessageBoxManager.Show() doesn't.
On the following link is demonstrated how you could avoid this behavior.
http://www.youtube.com/watch?v=XVbpYOsxJdg&feature=youtu.be
If this doesn’t work for you, please provide show us what exactly happen on your machine and also could you please provide us a sample that demonstrate your issue.
Hi Wolfgang,
Restarting VS does not change anything and the ToolsVersion is 4.0 in my project also.
However, it works anyway. Thanks for your help.
Kind regards
Thomas
Hi Thomas,
your problem is rather interesting since without the SubsystemVersion element being present in the project file the message boxes are not shown appropriately. I've tested that right now by commenting out the SubsystemVersion element and then the buttons touch the lower border of the message box. This means, that VS2012 seems to be confused about this element but when running it this works correctly. Have you tried to close and reopen VS which helps often when it shows weird warnings or behaviors on my machine?
I don't know what the ToolsVersion attribute in the root element Project is used for but this could maybe be also different? In my project ToolsVersion is 4.0
Regards Wolfgang
Hello Wolfgang,
I have attached an image showing the message in VS2012.
Anyway, it works fine now. I missed to disable host process when debugging as mentioned in an earlier post.
Many thanks,
I tried it now with a Playground project of mine, it works fine as a .NET 4.5 project and I'm using VS2012 update 3 as well which doesn't complain about invalid child element SubsystemVersion within element PropertyGroup. I've attached my Playground.csproj-file to this post, you can find the SubsystemVersion element on line 48. With that message boxes using UltraMessageBoxManager are shown correctly.
If needed I could also provide you with the entire project so that you can try to load that on your PC.
Regards, Wolfgang
Hello Hristo,
According to you video I tried to edit the project file with no luck.
VS2012 is telling me that I am using an invalid child element "SubsystemVersion" within the element "PropertyGroup"
I am using VS2012 Update 3 with TargetFramework 4.5
Any ideas?