I use the 9.2 Infragistics Suite and i use the AppStyling.StyleManager.Load function.
When i load my LOGIN FORM, i apply the template (ISL File) and it works then... when the user wants to change the theme, the method freeze... no exception, just freeze my application
the file exists and i'm sure that it already works...
Which isl file are you using? Is it one of the ones included with NetAdvantage, or is it one of your own?
Can you duplicate the freeze in a small sample project?
It is one that are included with netadvantage suite
here is the method that i use :
Public Function LoadStyleTemplate(ByVal aTheme As PStyleTemplate) As Boolean Dim themePath As New StringBuilder themePath.Append(Application.StartupPath).Append("\Assets\Styles\").Append(aTheme.Path) If themePath IsNot Nothing AndAlso File.Exists(themePath.ToString) Then AppStyling.StyleManager.Load(themePath.ToString) InfoSession.SelectedTheme = aTheme Return True Else Return False End If End Function
I've never heard of a case where loading an isl locks up the app. I'm not sure what could possibly be causing that.
My first recommendation is that you get the latest service release and see if that helps.
How to get the latest service release - Infragistics Community
If that doesn't help, then we will need to be able to duplicate the issue in order to find out what's happening. Perhaps you can create a small sample project that demonstrates the problem?
I know this is an old topic but I'm also having the same freezing issue with our application. I did recently open a ticket regarding this, as I only had the issue locally on my dev machine, however now we've had clients report the issue as we sent out an update to the application.
I'm using v16.2.20162.2111 of Infragistics WIN FORMS - so quite a few versions later than the original poster. When the application first loads I load in the theme, then a login form is displayed for the user, when the user logs in, it will then load the theme that the user has selected previously (filename saved in db), if no theme selected, then it will load our default theme again. As we don't supply any other themes to the user at the moment, it's always the default one.
Q) Can I pull the filename out of the stylemanager after it's loaded then maybe I don't need to load again if it's the same file???
I can't replicate this on a small demo app at all, and only had it locally a couple of times - mostly when running from VS2017 - when I break the code after it's hung it breaks on the line:
and won't continue on.
The clients we have that are reporting the issue seem to be on larger environments, and some on terminal servers running the same application, and possibly accessing the same file.
Is there anything in the Stylemanager code that could cause this hang??? I'm at a loss on what I can do at my end.
Having the same issue here:
Using version 18.1.20181.88
Completely freezes the application..no exception nothing.
Did you get an answer on this?
If you can reproduce this in an isolated sample, that would help us to understand what is happening. If you aren't able to do so, it might help to know if there is a more specific spot where the hang happens rather than just at Infragistics.Win.AppStyling.StyleManager.Load. Is there more to the call stack if you show external code?
It is also possible that you could get more information if you get a memory dump of the hung application and use the Debug Diagnostics Tool to analyze the dump (if you can't reproduce the hang in a sample).
I also recommend making sure that Infragistics.Win.AppStyling.StyleManager.Load is always called from the UI thread if you are doing any threading in your application.
I will try to isolate it. We have a really large program. The problem is the application just hangs...but now we found the exact line...turns out it is this:
When a user logs on...they can change the settings in their profile for styles. So when they logoff./on it runs this line to clear and reload.
First time logging on it hits this line...even though there is no style. It has never been an issue before..but that is where it is currently hanging. I can't get it to be consistent either but I will try and see if I can get you the call stack.
Running with debugging should allow you to pause the application while it hung and then copy and paste the call stack from the call stack window.